cannot connect after building

[rkuhn]

Following the development guide, I built the server (tried both with -tags dev and without) and started it:

level=debug starting=metrics addr=localhost:6078
loaded active.de.toml
loaded active.en.toml
level=info event=serving ID="@xsf/w1MO+xwujt5gbfqEdO25qDkE9v5vzOY2KhFWCsI=.ed25519" shsmuxaddr=:8008 httpaddr=:3000 version=v2.0.7 commit=unset

Connecting to it via http://localhost:3000 redirects to https://localhost:3000 which fails in Chrome (latest) with ERR_SSL_PROTOCOL_ERROR, no further info, nothing printed in the console. System is Debian 11.

If it matters: Chrome is running on macos using an SSH tunnel for port 3000.

How can I get out more debug info and/or solve this problem?

[decentral1se]

Hey @rkuhn, sounds like you maybe ran into https://github.com/ssbc/go-ssb-room/issues/356? You definitely want -tags=dev to avoid this HTTPS requirement for local testing. Did you try another browser? I wouldn't imagine the tunnel has much to do this with this but you might want to reduce the moving parts to track down this issue... good luck and do let us know!

[rkuhn]

Thanks, I got it working by using -tags=dev and purging the browser cache (the 301 → https was still in there). However, I also tried accessing the public IP, i.e. in non-local and non-testing mode, and the behaviour was the same. So setting up a proper Room is still something I can’t do.

The next hurdle is that any click on the served page goes to about:blank#blocked (i.e. a white screen). This behaviour persists also after creating the admin user.

[decentral1se]

@rkuhn

However, I also tried accessing the public IP, i.e. in non-local and non-testing mode, and the behaviour was the same. So setting up a proper Room is still something I can’t do.

Ah, you can't run a non-local / non-testing instance with -tags=dev? It's only for local dev mode?

(if you're seeing this issue on a not -tags=dev build, let's open a new issue with more details?)