Nginx Connection refused after update from RC3

[shipler]

After updating from RC3 to the latest version using local iso mounting, the nginx is getting the following in the so/log/nginx/error.log -

connect() failed (111: Connection refused) while connecting to upstream, client x.x.x.x, server: _, request: "XXXXX"

When accessing the master web port i get "502 bad gateway" error, also tried restarting the OS but the error persists

[TOoSmOotH]

What does so-status show?

[shipler]

so-soc ERROR, and now the nginx error is "Authorization Required 401". I'm going to reinstall the cluster...

[shipler]

Reinstalled the Master server, same error. so-soc not starting. and there's no logfile in the log/soc folder. how can I debug this?
The docker ps command not showing so-soc image

[shipler]

docker logs so-soc showing error:

Error: Unable to read configuration file 'sensoroni.json' [invalid charachter '\n' in string literal]
error Syntax error reading json object error=invalid charachter '\n' in string literal offset=814

[TOoSmOotH]

4a9fcfb should fix the issue. Just make the same change. This will be fixed in 2.3.1

[shipler]

Yep, same error. Thanks!

[ColeVan]

I'm getting the exact same errors when trying to access the SOC page. Is there a way to remedy this?

There are no log files in the soc directory to troubleshoot. nginx error.log shows the same error as above.

[TOoSmOotH]

Run soup. This is fixed in 2.3.1

[ColeVan]

Will this also update the nodes connected to the existing manager if soup is ran?

[TOoSmOotH]

yes

[ColeVan]

Once I update and try to login I get this error. Any thoughts?

The login request has expired. Redirect the user to the login endpoint to initialize a new session.

And then when you go to login with the cred I get this error

{"error":{"code":400,"status":"Bad Request","reason":"CSRF token is missing or invalid.","message":"The request was malformed or contained invalid parameters"}}

[TOoSmOotH]

Please open a new discussion for your issue. It is unrelated to this one.