Rocket chat fails to load the Apps window and the Marketplace window in the “Administration” pane. It does display a blank red error window but it doesn’t print into that any error message. As per screenshots below:
No current logs at the time being.
Where should I look for them in the system if you need a copy?
The server has access to the internet, (VPS). No proxy needed.
That part works fine. Can connect both through browser and the chat client and do various tasks too. But the app store is the thing that fails to load.
(It used to work in the past just FYI)
We have deployed it through snap our own Ubuntu Linux VPS server.
That is not possible I suppose because we are not hosted by you guys, but self hosted/on-premise.
(Or did I misunderstand your thinking about the above?)
the idea of traceroute is to see if you have connectivity to our cloud.
you can run, at the server terminal:
traceroute cloud.rocket.chat
this will show all the path of a request to touch our cloud server. You may want to send this to me in private, or redact the initial IPs so you don’t unveil your production IP
I know this topic is a few months old, but did you ever resolve your Problem?
I have recently moved our Rocketchat from Snap 3x to Docker 5.x behind a NAT and reverse proxy, everything is working fine except for App Store and Cloud Sync which time out upon usage. The weird thing is, i can log into the cloud service and it registers fine, but then fails to sync because of
I can curl and traceroute cloud.rocket.chat just fine from the server and i don’t see any initial NAT issues that would cause the packets to be dropped.
Yes, i am facing the same issue with a completely new deploy and no restored DB’s, in fact, i cannot even register the new server during the initial setup process due to this issue.
Packet sniffer shows that Packets from the cloud.rocket.chat IP are incoming and get forwarded to the correct server on port 5100. I also tested the snap install from a restore in the same network and the marketplace connected fine there, even though i didnt have any proxies set up to point to that installation.
Very confused as to where the rootcause of this issue lies since i don’t run any additional FW’s server side.