Repository navigation
Closed
Labels
BugType: existing behavior is wrongType: existing behavior is wrong
Description
What Happened?
I have followed all the steps on the Deployment guide (which maybe could use an update) with the latest main version. I am getting the following error when setting up the gateway container, which is preventing the complete deployment of the application:
root@alta-vm:/home/frolesti4_gmail_com/OpenDataCapture# docker logs open-data-capture-gateway-1
Server started at http://localhost:80
Server started at http://localhost:80
ReferenceError: document is not defined
at Translator.changeLanguage (file:///app/dist/server/entry-server.js:31116:5)
at Translator.replacementMethod (file:///app/dist/server/entry-server.js:31087:19)
at Translator.init (file:///app/dist/server/entry-server.js:31130:10)
at file:///app/dist/server/entry-server.js:107047:6
at ModuleJob.run (node:internal/modules/esm/module_job:345:25)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:665:26)
at async file:///app/dist/main.js:74083:26
[01:06:48.611] ERROR (1): request errored
req: "GET /"
res: 500
responseTime: 549
err: {
"type": "Error",
"message": "failed with status code 500",
"stack":
Error: failed with status code 500
at onResFinished (file:///app/dist/main.js:50710:46)
at ServerResponse.onResponseComplete (file:///app/dist/main.js:50761:18)
at ServerResponse.emit (node:events:531:35)
at onFinish (node:_http_outgoing:1082:10)
at callback (node:internal/streams/writable:766:21)
at afterWrite (node:internal/streams/writable:710:5)
at afterWriteTick (node:internal/streams/writable:696:10)
at process.processTicksAndRejections (node:internal/process/task_queues:89:21)
}
root@alta-vm:/home/frolesti4_gmail_com/OpenDataCapture#
Is this something known? I am having a lot of issues with the deployment. I was able to deploy it two weeks ago with another version of main, something must have changed.
What Did You Expect?
I expect the gateway container to initiate properly
Operating System
Ubuntu 25.04
Browser (if applicable)
Chrome
Steps to Reproduce
No response
Anything Else?
No response
Metadata
Metadata
Assignees
Labels
BugType: existing behavior is wrongType: existing behavior is wrong
Activity
joshunrau commentedon Oct 1, 2025
Thanks for the report. I will have a look now.
joshunrau commentedon Oct 1, 2025
This issue should now be fixed in v1.11.2. It was due to a change in one of our libraries. Please update to that version.
frolesti commentedon Oct 1, 2025
Hi @joshunrau
Thank you for your short response time, it is really appreciated. The thing is that I am still seeing the same error:
When setting up the containers, it looks like it is properly set. But then, eventually this error appears again.
frolesti commentedon Oct 1, 2025
I take it might be an issue of my set up?
I changed the server Linux provider to Ubuntu 22.04 but to no use, I have been following the deployment guides so everything seems to be in place.
gdevenyi commentedon Oct 1, 2025
In order to provide better support here. Can you please describe the entirety of your setup process, this means:
Thanks.
joshunrau commentedon Oct 1, 2025
Could you please also confirm that the version is updated to 1.11.2. I replicated this issue on our demo and updating the version fixed it. Did you run
docker compose downand thendocker compose up -d. I don't thinkdocker compose restartwill use the latest images.frolesti commentedon Oct 1, 2025
Hi guys, thank you for your interest!
This is my .env file:
This is my /etc/caddy/Caddyfile:
I have been following the guide step by step. I set up a VM in Google Cloud, install Linux, Docker and Caddy. Then, I clone my forked repository, execute the generate-env script succesfully and change the
.envto point into my domain. Then executedocker compose up -d. At first, it looks like the gateway is properly listening to the localhost:80 port, but eventually this error appears when executing docker logs open-data-capture-gateway-1.Is there anything I am missing?
thomasbeaudry commentedon Oct 2, 2025
did you try doing a docker compose pull?
gdevenyi commentedon Jun 9, 2026
Triaging upstream: deployment/runtime versions have changed substantially since this issue was opened. Is this gateway startup error still reproducible on the current version in Google Cloud VM? If so, please add current logs and deployment details.
joshunrau commentedon Sep 16, 2026
Closing as irrelevant: the underlying SSR bug (document is not defined) was fixed in v1.11.2. The residual report traced to the reporter's stale deployment config (old compose format, missing services) rather than a defect in the current stack, and a maintainer already flagged this as likely stale with no reply since.