It is very likely that this can be solved, but slight modifications to some server parameters. The NOMAD Oasis runs an nginx reverse proxy as gateway to the different services.
To get a general idea how long an upload is supposed to take: nomad is writing the file down while receiving it. An upload request should only take as long as the network bandwidth between client and nomad and the write-speed of the used filesystem suggests.
If you run another reverse proxy in front of the NOMAD Oasis, try to figure out which proxy is causing the timeout, the NOMAD Oasis nginx, or your reverse proxy.
The NOMAD nginx is configured by the configs/nginx.conf that you probably have downloaded from the NOMAD documentation (here)[Operating an OASIS - NOMAD Documentation]. It contains a rule for the upload API endpoint. This is were the timeout most likely is originating from. It should look something like this:
Thanks for the quick reply, I’ll take a look into these options and report back if we manage to fix the issue.
We are not using an additional reverse proxy next to the one that came with the docker deployment and The error was reported by one of our users, who tried to upload the file via the UI.
This however also raises the question on how to update our instance, If I understand the documentation correctly the default is to just update the docker image. But how wil required l changes to the files in the original zip archive (docker-compose.yml, nginx.conf, …) be communicated if they should become necessary?
Yes, mostly it would just mean to use a new image tag. There is still an upcoming major release. As part of it, we are revising the availability of a Changelog that would inform about necessary config changes.