Replies: 2 comments
-
|
hello @hk05418 , please ask to discord tech https://discord.gg/blockscout |
Beta Was this translation helpful? Give feedback.
-
|
Blockscout’s Docker proxy container communicates internally with backend & frontend only through port 80. 👉 Therefore: ❗ You MUST NOT change target: 80 If you change it: Wallet login gets stuck Backend API fails Blocks stop loading You get 500 / 501 errors Auth0 integration breaks ✔ The correct solution Keep the internal port = 80, Correct Docker mapping: ports:
target (inside container) → always 80 published (external host port) → 443, or any other port you want 💡 Why does this work with your Nginx config? Because your external reverse proxy defines: server { This: Handles HTTPS Routes backend paths (/api, /socket, /auth/...) Routes frontend (/) Routes stats + visualizer services Then Nginx forwards traffic to the container’s internal port 80: proxy_pass ${BACK_PROXY_PASS}; So external users reach 443 → Nginx → Blockscout container → port 80. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Must port 80 be used? After changing the port, it won't take effect. If the port is not changed, the block information can be obtained. But after the change, the block information cannot be obtained and can only be obtained through port 80

After the modification, the acquisition of block information failed
Beta Was this translation helpful? Give feedback.
All reactions