sebw / pushtify

Listen for Gotify notifications over websocket and forward them to Pushover
30 stars 6 forks source link

110 Operation Timed Out | Pushtify Container Runs but does not Forward Messages to Pushover? #3

Closed stryk3rr3al closed 1 month ago

stryk3rr3al commented 1 month ago

Error [Errno 110] Operation timed out

closed

A couple of things worth noting -I'm using port 23606 to expose Gotify to the web via an NGINX proxy manager, Gotify it's self is only configured to use HTTP, the proxy is handling the SSL portion. -I can post messages to my Gotify endpoint via the Nginx proxy URL and they arrive just fine.

Environment Variables GOTIFY_TOKEN=GotifyClientToken GOTIFY_HOST=notify.redacteddomain.xyz:23606 PUSHOVER_USERKEY=Userkey PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Any troubleshooting steps or guidance is appreciated.

stryk3rr3al commented 1 month ago

Firewall rule was blocking the connection to the NGINX proxy in my network. Simple fix was to create a pass rule for the proxy port / address.

Now I'm getting a different set of errors that seems to be related to my NGINX config

closed

Handshake status 403 Forbidden -+-+- {'server': 'nginx', 'date': 'Wed, 15 May 2024 23:24:36 GMT', 'content-type': 'application/json', 'content-length': '0', 'connection': 'keep-alive', 'x-xss-protection': '1; mode=block', 'x-content-type-options': 'nosniff', 'strict-transport-security': 'max-age=63072000; includeSubDomains'} -+-+- b''

stryk3rr3al commented 1 month ago

After setting the two Gotify environment variables below and then making changes to allow websocket connections in NGINX I'm up and running.

Environment variables GOTIFY_SERVER_STREAM_ALLOWEDORIGINS GOTIFY_SERVER_CORS_ALLOWORIGINS