Reverse Proxy - 400 Bad Request

[EVOTk]

Can the issue be reproduced with the latest available release? (y/n) y

Which one is the environment gotify server is running in?

• [X ] Docker Synology DSM 6

My Compose :


Do you have an reverse proxy installed in front of gotify server? (Please select None if the problem can be reproduced without the presense of a reverse proxy)

• None
• [ X] Nginx
• Apache
• Caddy

In Synology Proxy Header :

Upgrade $http_upgrade
Connection "upgrade"
X-Real-IP $remote_addr
X-Forwarded-For $proxy_add_x_forwarded_for
X-Forwarded-Proto http
Host $http_host

On which client do you experience problems? (Select as many as you can see)

• WebUI
• gotify-cli
• [ X] Android Client
• 3rd-party API call (Please include your code)

What did you do?
Remote Connection

What did you see instead? (Include screenshots, android logcat/request dumps if possible)

I sometimes receive notifications, and I often get "Bad Request" error messages

[jmattheis]

Please also add your gotify/server log output.

[EVOTk]

Thx for your reply ! in log gotify/server i'm found :

Error #1: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header

In my reverse proxy, i'm change :
Connection "upgrade"
to
Connection upgrade

and the error is no longer there! the "Bad Request" error has disappeared!
Do you think it is useful to add an intermediate docker on my syno, in order to have a proxy with parameters like:
proxy_connect_timeout 7m;
proxy_send_timeout 7m;
proxy_read_timeout 7m;

That it is not possible to include basic in Synology?

[jmattheis]

Gotify should work without these parameters.

[EVOTk]

Thx for your reply