Connections realtime not working anymore in 2.0.20 pro

[Alexander]

I have updated to 2.0.20 pro and since then, realtime connections are not working anymore. When I check the browser console, i see: (index):431 WebSocket connection to 'wss://xxx.xxxxx.xx/admin/ws' failed: Error during WebSocket handshake: Unexpected response code: 500

[Alexander]

Just checked: When calling https://demo.poste.io/admin/ws/, some Haraka status is displayed, when I call this on my installation, I get ERROR 500

[SH]

Can you please look into data/log/admin-app/prod.log? There should be info about error - I suspect that you have something different in your setup due upgrades/settings and thats why I can't replicate that. I'm almost sure it is same issue as #525

[Alexander]

I suspect that too ... What's very strange, the latest Enty in the prod.log is from yesterday: [2018-11-28 22:58:44] security.DEBUG: Stored the security token .... Since then, it does not update the prod.log file anymore- i have already restarted the container, but it makes no difference

[Scott MacDonald]

Try removing and recreate the container.

[Alexander]

What came to my mind. Since 2.0.20 pro, I changed running poste.io in docker bridge mode using the env variables HTTP_PORT and HTTPS_PORT that were introduced in 2.0.19 - I use them to set them to other ports so they don't conflict with port 80 and 443 that are already in use on the host system. On the host, I use a nginx reverse proxy to make the web part of poste available on port 443. I wonder if this causes the issue as the possibility to set the HTTP_PORT and HTTPS_PORT variables is a relatively new feature.

[SH]

Jackpot. These two services are internaly redirect WITH subrequest to authorization - and this authorization is on different port with your setup.

[SH]

return zero if item guard item not found (ref #522)

→ <<cset 93ecf611c852>>

[SH]

add HTTPS_PORT and HTTP_PORT settings to internal redirects also (fix #522 and fix #525)

→ <<cset 3a33ac651ace>>

[Alexander]

Great we tracked it :-) Looking forward to the updated poste!

[SH]

fix #522 use awk to parse default interface

→ <<cset adf1664aa7f5>>

[SH]

fix #522 use only first row of route default output

→ <<cset 6b28bb4ffc50>>