Forum

Hello, from our side, visiting the firstprinciples.zeabur.app is fine. Can you give me more details?

Hi, I want to say upfront that two weeks of fighting with this is genuinely frustrating, and I'm sorry you've been stuck. You're not doing anything wrong — OpenClaw is a complex piece of software with a lot of moving parts (gateway, Control UI, model providers, Telegram pairing), and we hear you.

Worth flagging separately: based on recent feedback (including yours), we found that older OpenClaw versions had several bugs causing slow and unresponsive behavior. We just released v2026.5.4 to fix those. Your service is currently on v2026.4.5, so picking up the new version will likely smooth out a lot of the "getting worse" feeling you described — happy to help you redeploy to the latest version once we get past the issue below.

Now the actual good news: you do not need to erase your config. Your service OpenClaw-enes is almost fully set up — it's running, firstprinciples.zeabur.app has a valid certificate, your OpenRouter API key is set, and your Telegram pairing code is already configured. The three symptoms you described (the page that looks like an SSL error, the empty models dropdown, and Telegram not finishing setup) aren't three separate problems — they're all the same single missing step. The OpenClaw Control UI needs the gateway token pasted in once. Until that's done the page loads but the WebSocket to the gateway is rejected, so nothing inside the panel can populate. That's why it feels like everything is broken when really only one thing is.

Here's how to finish in under a minute:

1. In the Zeabur dashboard, open OpenClaw-enes → Variables tab → copy the value of OPENCLAW_GATEWAY_TOKEN.
2. Open https://firstprinciples.zeabur.app in your browser.
3. Paste that token into the Gateway Token field on the page.
4. Click Connect.

Once it connects, the models dropdown will populate and the Telegram setup will be usable. Each browser/device only needs to be paired once — that's by design, not a bug. After that's working, let me know and I'll walk you through updating to v2026.5.4 too.

wow , again, once i click on a link it takes me to an error ssl error page. ive tried it with http:/ and https:/ in 3 different browsers

Got it — I confirmed your URL is exactly https://firstprinciples.zeabur.app (correct), and we just tested again from our side and it loads fine (HTTP 200 with valid SSL cert). So the URL is right, the server is right, the cert is right.

The SSL_ERR_RX_RECORD_TOO_LONG / ERR_SSL_PROTOCOL_ERROR appearing only on your machine in 3 browsers means it's a client-side / network issue, not Zeabur's. Things that could cause this when the server is fine:

Most likely causes (please try in order):

1. Antivirus or firewall doing SSL inspection ⚠️

This is the #1 cause when "all browsers fail but the site works for everyone else". Some antivirus software (Avast, AVG, Kaspersky, ESET, BitDefender) and corporate firewalls intercept HTTPS to scan it, but their fake cert/decryption can mangle the response into RX_RECORD_TOO_LONG.

→ Try temporarily disabling your antivirus's "HTTPS scanning" / "SSL inspection" / "Web shield" feature, then refresh. If the page loads, that's the culprit.

2. Corporate / school / coffee-shop network

Same as above but at the network level — some networks intercept HTTPS for content filtering.

→ Try switching to your phone's mobile hotspot (4G/5G). If the site works on hotspot, your current network is intercepting traffic.

3. VPN / proxy / DNS-over-HTTPS

→ Disable any VPN you have running, disable browser-level proxy settings, disable DoH temporarily

4. System-level issue

• Check your laptop's date/time is correct (off by hours = TLS rejects)
• Try a different device entirely (your phone on cellular). If it works on phone but not laptop → laptop has the issue, not network.

Diagnostic to confirm where the problem is:

Open Terminal/Command Prompt on your laptop and run:

curl -v https://firstprinciples.zeabur.app 2>&1 | head -30

If curl ALSO fails with TLS error → it's your laptop / network (not browser). If curl WORKS but browsers fail → it's browser-specific (extensions, cache, etc.).

Paste the curl output here and I can pinpoint exactly which layer is breaking the connection. From our side everything's confirmed working, so we just need to find which layer between you and us is interfering.

at hoe no antivirus or firewall or vpn,

going down your list, i ran into a good connection, by using my phone , without using my home wifi. i use my mobile data, and it connected.....so i then used my phone as a hotspot, it also connected. ill just use my hotspot for now, if you can think of why this worked, let me know....i had been using my home wifi before to connect a while ago....something must have changed with the isp

this gives me at least a starting point to figure some things out, also, i tried to update the openclaw a couple of times, but it keeps the old one, can you update it for me...

You can update version from service settings, change the version you want, for example from 2026.4.5 to 2026.5.4

This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.