Can't open it on mobile

[Samiya321]

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

No response

👟 Reproduction steps

Typing in a link on my iphone's safari browser and then entering, it doesn't show the page properly, it's blank

👀 Expected behavior

Display page content normally

😓 Actual Behavior

empty space

Dockge Version

latest

💻 Operating System and Arch

Ubuntu 22.04 x64

🌐 Browser

Safari

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[Samiya321]

Cannot reproduce, please try https://uptime.kuma.pet

I built my own uptime kuma and it opens fine on my phone
But dockge doesn't show up properly on the mobile side

[louislam]

iPhone 15
iOS 17.1

[Samiya321]

I tried it on iPhone 13 / iOS 16.2 and iPhone 13 / iOS 15.1 and it won't open

[Tooa]

Hi 👋,
dockge (docker install, version: 1.3.5) also does not load for me on my iPhone 7 with iOS 15.8 (Safari, Firefox iOS 121 build 36782, Chrome iOS 120.0.6099.119). The page "https://uptime.kuma.pet/" works fine on my iPhone with Safari though.

When accessing dockge nothing shows in the log. In contrast, accessing dockge with my notebook shows:

dockge  | 2023-12-23T22:06:54Z [SERVER] INFO: Socket connected!
dockge  | 2023-12-23T22:06:54Z [AUTH] INFO: Disabled Auth: auto login to admin

Any chance to make the dockge server more verbose in the logs? Let me know if you need further information!

Appendix

Access via http://:<5001>

version: "3.8"

services:
  dockge:
    image: louislam/dockge:1
    container_name: dockge
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./data:/app/data
      - /opt/stacks:/opt/stacks
    environment:
      # Tell Dockge where to find the stacks
      - DOCKGE_STACKS_DIR=/opt/stacks
    ports:
      - "5001:5001"

[opticsthewebsite]

Just tried on my iPhone 14 with latest iOS. Works fine with the latest versions of Chrome and Safari.

[Tooa]

Thanks for reporting. I assume the problem has something to do with older iOS/WebKit versions.

Do you have a device with iOS < 17.x to validate the assumption?