a month ago
I installed my openclaw app and is perfect running and connecting from the computer I installed from with my railway app. when I go to a second computer and try it, the gateway says invalid token, even when I grab the token from inside of my railway app.
still works on the first computers browser.
but if i open a second broswer from same computer, I get the same issue. no token works
I would have assumed the same token worked across all devices. hence the reason for a secure token?
7 Replies
Status changed to Open Railway • about 1 month ago
a month ago
2026-04-19T03:00:31.905+00:00 [ws] closed before connect conn=5877f2cd-faf4-42ce-8247-a390c360cbd1 remote=127.0.0.1 fwd=167.82.135.24 origin=https://openclaw-railway-template-easy-config-production-f722.up.railway.app host=openclaw-railway-template-easy-config-production-f722.up.railway.app ua=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36 code=1008 reason=unauthorized: gateway token mismatch (open the dashboard URL and paste the token in Control UI settings)
2026-04-19T03:00:35.180+00:00 [ws] unauthorized conn=9b5c78af-fa52-4e5f-bd1c-bca8fcea0161 remote=127.0.0.1 client=openclaw-control-ui webchat v2026.3.28 reason=token_mismatch
2026-04-19T03:00:35.486+00:00 [ws] closed before connect conn=9b5c78af-fa52-4e5f-bd1c-bca8fcea0161 remote=127.0.0.1 fwd=167.82.135.82 origin=https://openclaw-railway-template-easy-config-production-f722.up.railway.app host=openclaw-railway-template-easy-config-production-f722.up.railway.app ua=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36 code=1008 reason=unauthorized: gateway token mismatch (open the dashboard URL and paste the token in Control UI settings)
2026-04-19T03:00:40.178+00:00 [ws] unauthorized conn=2ca80259-5c33-41ab-9cd0-78ac984c1359 remote=127.0.0.1 client=openclaw-control-ui webchat v2026.3.28 reason=token_mismatch
2026-04-19T03:00:40.457+00:00 [ws] closed before connect conn=2ca80259-5c33-41ab-9cd0-78ac984c1359 remote=127.0.0.1 fwd=167.82.135.79 origin=https://openclaw-railway-template-easy-config-production-f722.up.railway.app host=openclaw-railway-template-easy-config-production-f722.up.railway.app ua=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36 code=1008 reason=unauthorized: gateway token mismatch (open the dashboard URL and paste the token in Control UI settings)
despite copying the token from the variables, this is what it does. not sure about this railway app
a month ago
Hello simplyict,
log says "open the dashboard url and paste the token in control ui settings." so instead of copying from railway variables, try opening the dashboard url in your working browser first, then paste that token into the control ui settings on the second computer
Hope this help you :)
a month ago
Hi Domehane
I am not using tokens. I am using a password.
simplyict
Hi Domehane I am not using tokens. I am using a password.
a month ago
but your logs are showing "gateway token mismatch" not a password error , am i missing smth here ?
a month ago
yes, it always says that. even if you are using a password. believe me, that is happening on my other desktop. however you are all correct. I am using a token on this unit, not a password which is different to my other installation. this system refuses to accept the token.
a month ago
so removed the current app and rebuilt. all good. access web ui and logs in immediately on google chrome. if I use another broswer and access the webapp even logging in to that broswer on the railway app and clicking the built link, it refuses to login saying token mismatch, even if I paste the current token into the ui. same thing
a month ago
what i know is that each browser has its own separate session storage, so the token doesn't carry over between chrome and another browser even if you paste it manually
try opening the exact dashboard url with the token already in it (the full url from chrome including any token parameter) directly in the other browser instead of navigating to it fresh and pasting the token manually