[Help]: Some setting page don't load

[Alfonso0p6]

Controller Version

5.13.22

Describe the Bug

some settings pages do not load

Expected Behavior

pages loading correctly

Steps to Reproduce

1. Start the container,
2. Login
3. Open the settings

How You're Launching the Container

docker run -d \
  --name omada-controller \
  --restart unless-stopped \
  --ulimit nofile=4096:8192 \
  -p 8088:8088 \
  -p 8043:8043 \
  -p 8843:8843 \
  -p 27001:27001/udp \
  -p 29810:29810/udp \
  -p 29811-29816:29811-29816 \
  -e MANAGE_HTTP_PORT=8088 \
  -e MANAGE_HTTPS_PORT=8043 \
  -e PGID="508" \
  -e PORTAL_HTTP_PORT=8088 \
  -e PORTAL_HTTPS_PORT=8843 \
  -e PORT_ADOPT_V1=29812 \
  -e PORT_APP_DISCOVERY=27001 \
  -e PORT_DISCOVERY=29810 \
  -e PORT_MANAGER_V1=29811 \
  -e PORT_MANAGER_V2=29814 \
  -e PORT_TRANSFER_V2=29815 \
  -e PORT_RTTY=29816 \
  -e PORT_UPGRADE_V1=29813 \
  -e PUID="508" \
  -e SHOW_SERVER_LOGS=true \
  -e SHOW_MONGODB_LOGS=false \
  -e SSL_CERT_NAME="tls.crt" \
  -e SSL_KEY_NAME="tls.key" \
  -e TZ=Etc/UTC \
  -v omada-data:/opt/tplink/EAPController/data \
  -v omada-logs:/opt/tplink/EAPController/logs \
  mbentley/omada-controller:5.13

Container Logs

logs attached

MongoDB Logs

logs attached

Additional Context

output.log
mongod.log

[mbentley]

I can only imagine that this is a browser issue - these pages load fine here. Check with your browser's dev tools to see if there is some reason why pages aren't loading (frontend errors, API backend errors, etc), try another browser, or clear your cache.

[Alfonso0p6]

i have this cloudflare tunnel setuped.

this is the browser console

[mbentley]

It could be a few things.

Not sure if the cloudflare tunnel is acting as a load balancer/ingress in front of your controller but maybe web sockets aren't working through it. Can you bypass the cloudflare tunnel in place to check? Might want to check the dev tools network tab and see if your browser has a "websocket" or "ws" filter to just show the websocket traffic to make sure it isn't returning an error. You should see a 101 http response like:

Another thing could just be a browser extension blocking some of the javascript from loading but I am leaning toward the first issue.

[Alfonso0p6]

sorry for bothering you, u were right it's cloudflare that in some way is blocking websocket, accessing from the ip works fine