[Bug]: Unable to load resource on iPad Safari

[shp7724]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Safari
• Local OS: iPadOS
• Remote OS: macOS
• Remote Architecture: arm64
• code-server --version: 4.6.0

Steps to Reproduce

1. open code-server
2. login

Expected

The editor should load.

Actual

White blank page.

Logs

...
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/browser/browser.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/cancellation.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/marshalling.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/event.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/lifecycle.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/parts/request/browser/request.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/resources.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/uri.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/platform/product/common/product.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/network.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/platform/window/common/window.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/strings.js
File not found: /opt/homebrew/Cellar/code-server/4.6.0/libexec/lib/vscode/out/vs/base/common/path.js

Screenshot/Video

Does this issue happen in VS Code or GitHub Codespaces?

• I cannot reproduce this in VS Code.
• I cannot reproduce this in GitHub Codespaces.

Are you accessing code-server over HTTPS?

• I am using HTTPS.

Notes

• On macOS, everything works fine no matter which browser I use.
• I tried reinstalling code-server several times.
• If I refresh a lot of times, strangely it works sometimes. But most of the time it doesn't. I think the odds are lower on PWA mode.

[jsjoeio]

This is very strange 🤔 How are you doing this exactly?

1. install via homebrew on macOS
2. expose and access on iPad?

[shp7724]

Yes, I installed via homebrew and enabled HTTPS using nginx and certbot.

I managed to (temporalily) solve this issue by going through the whole installation process twice, which includes reinstalling everything(i.e. code-server, nginx, certbot) and reissuing ssl certificates. Reinstalling only one of them didn't solve the issue.

As far as I remember, I started seeing this issue when my ssl certificate got expired and reissued a new one. I don't see how it can be associated with this issue, though. :(

[jsjoeio]

I guess what would be helpful for me is to know how to reproduce this. Would these steps suffice?

1. install code-server on macOS via homebrew
2. run ngrok to expose code-server
3. open on iPad in Safari

[shp7724]

@jsjoeio It's been a quite a while, but I'm still suffering from this issue. The steps you suggested doesn't seem to be enough to reproduce it.

One thing I noticed though, is that all the failed requests are missing a cookie named code-server-session.

For instance, the following request succeeded with the cookie code-server-session:

whereas this request didn't (note the entire cookie is missing here):

If I copy the request as cURL and manually attach the same code-server-session cookie, it does seem to work.

I suspect this might have something to do with the internal session management mechanism of iPadOS safari.

[shp7724]

Temporarily disabling and reenabling Prevent cross-site tracking option in settings, everything started to work as expected. 🤯😮

[jsjoeio]

Nice find!!! Can we close this now?

[shp7724]

@jsjoeio

It turned out to be a coincidence, I'm afraid. 😔

[jsjoeio]

Darn it :( Okay well sadly, I don't have bandwidth to dive in now but feel free to leave comments here and I can be your async rubber duck

[code-asher]

I have seen this happen on a slow network where the bundle takes a while to load. It times out and tries to load the sources individually, which do not exist of course.

Closing but see #2407