localhost:3000 no longer working

[zhushuihua]

xxx.xxxx.xxx.xxx/3000 is messy with latest versions.
All directs to https.

[ruggi99]

Can you be a little more specific?
It's not clear what you mean

[AVanVlack]

I believe I am seeing this same issue. Studio is prefixing the URLs for all resource with https, instead of http, resulting in SSL errors for all resources after the initial page request.

This is happening for me on a new docker deployment of the latest build. The only change was the SUPABASE_PUBLIC_URL=http://192.168.1.11:3000 in .env

[ruggi99]

@AVanVlack Hi,
please post a screenshot of this path: http://172.16.42.52:3000/api/props/project/default/api.
Redact any sensible information, service key for example if you have changed it
Thanks

[ruggi99]

From what I see from the screenshot it seems an issue with SSL on the frontend, not backend.
It can't load fonts or needed javascript to work properly.
Seems like you tried to add SSL on frontend but it is misconfigured. Supabase self-hosted provides no SSL support AFAIK.
Can you please describe how you setupped Supabase self-hosted?

Thanks

[AVanVlack]

Here is props route with defaults:

The client is directly requesting from the server on the hosting port. No SSL proxy or anything in-between.

Instructions where followed from self host guide:

git clone --depth 1 https://github.com/supabase/supabase
cd supabase/docker
cp .env.example .env
docker compose up 

This setup was working with a build about 5 months old before removing all everything and reinstalling.

[AVanVlack]

Ahh I think I see the issue. The initial request is sending a upgrade-insecure-requests on the Content-Security-Policy header:

It looks like it was added in #11932

[ruggi99]

Graat work!
I think you found it.
Will send PR disabling it for self-host

Thanks

[AVanVlack]

Thank you!

[zhushuihua]

The issue is still there. Why it is now closed?

[ruggi99]

The issue seems to be fixed but it is not deployed yet.
A maintainer should build the image, upload to Docker Hub and include in docker-compose.yml
By now you have two alternatives:

• Build locally yourself studio image
• Downgrade pre-built studio image to at least one week ago.

[sweatybridge]

The fix is released in latest studio build 20230127-6bfd87b (timestamp was wrong but build is ok)

You can update the image version used by docker-compose file here https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml#L12. If you are happy with the fix, please consider sending a PR. I would appreciate your help as I cannot merge my own PR.

[ruggi99]

Interesting the wrong timestamp, it confused me. I didn't see Docker Hub telling me it was uploaded 4 hours ago.
Will send a PR.