fix nginx config for UI 2.0 websocket

[chrisciszak]

GitHub keywords to close any associated issues

Motivation

The UI 2.0 is not working with the current blockscout nginx config - it fails on the websocket giving consistent errors

Changelog

Enhancements

Things you added that don't break anything. Regression tests for Bug Fixes count as Enhancements.

Bug Fixes

Done

Incompatible Changes

Things you broke while doing Enhancements and Bug Fixes. Breaking changes include (1) adding new requirements and (2) removing code. Renaming counts as (2) because a rename is a removal followed by an add.

Upgrading

If you have any Incompatible Changes in the above Changelog, outline how users of prior versions can upgrade once this PR lands or when reviewers are testing locally. A common upgrading step is "Database reset and re-index required".

Checklist for your Pull Request (PR)

• I added an entry to CHANGELOG.md with this PR
• If I added new functionality, I added tests covering it.
• If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
• I checked whether I should update the docs and did so by submitting a PR to https://github.com/blockscout/docs
• If I added/changed/removed ENV var, I submitted a PR to https://github.com/blockscout/docs to update the list of env vars at https://github.com/blockscout/docs/blob/master/for-developers/information-and-settings/env-variables.md and I updated the version to master in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.
• If I add new indices into DB, I checked, that they are not redundant with PGHero or other tools

[vbaranov]

@chrisciszak it looks like this setup still will throw errors like:

WebSocket connection to 'wss://localhost/socket/v2/websocket?vsn=2.0.0' failed: 

until SSL is not enabled

[chrisciszak]

Thanks for checking in.

Shouldn't you call ws:// endpoint instead of wss if you are not on secure connection?

This PR adds a missing nginx config which is not related to secure connection. There is a config that specifies if you want ws or wss.

I'm happy to add it if you still want it with the explanation above.

@chrisciszak it looks like this setup still will throw errors like:

WebSocket connection to 'wss://localhost/socket/v2/websocket?vsn=2.0.0' failed: 

until SSL is not enabled

[vbaranov]

Thanks for checking in.

Shouldn't you call ws:// endpoint instead of wss if you are not on secure connection?

This PR adds a missing nginx config which is not related to secure connection. There is a config that specifies if you want ws or wss.

I'm happy to add it if you still want it with the explanation above.

@chrisciszak it looks like this setup still will throw errors like:

WebSocket connection to 'wss://localhost/socket/v2/websocket?vsn=2.0.0' failed: 

until SSL is not enabled

Ok, in order to make websockets work, we should add NEXT_PUBLIC_API_WEBSOCKET_PROTOCOL='ws' for the frontend. I will do in frame of #7841. Thank you for contribution.