I have another question about the problem “502 Bad Gateway” after the update and the change in the dtable_server_config.json with the API Gateway.
The topic has already been discussed in this post: First post in the forum
and there is another link to this post: Second post in the forum
which describes a solution to the problem.
Basically, you can say that the proposed solution works, but is it really correct? Every time I perform a restart with: docker exec -it seatable-server /shared/seatable/scripts/seatable.sh restart
I get the error “502 Bad Gateway” when opening a base and then have to: docker exec -d seatable-server /shared/seatable/scripts/seatable.sh stop
and docker exec -d seatable-server /shared/seatable/scripts/seatable.sh start
to fix the problem.
Unfortunately, I don’t understand if this needs to be done further in the future or if I still have a bug in my configuration that I need to fix?
Why do not start or restart docker image with docker command like “docker compose down”, “docker compose up -d”? This will make sure the docker container is started in a clean state.
If you say that’s the better way, then I’ll use it.
Just as an example of why I used the other command. In the documentation “Extra upgrade notice” it says about the Api Gateway that you should perform the following step after the change:
Afterwards, restart SeaTable with:
Then the error “502 Gatway” appeared and the suggested solution fixed the error.
However, since it can always happen after changes in the configuration that SeaTable has to be restarted, I wanted to test whether it works properly again and found that the error keeps coming back.
Hence the question of whether I have an error in my configuration or how I should deal with it in future.
There may be a bug that “docker exec -it seatable-server …” can not correctly start the api-gateway component (maybe it is because the old instance is still running).
I suggest after modifying configurations, the best way is to restart the service by docker compose command.
