-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Http page error #50
Comments
+1 for this. Is it possible to configure content for the root / of the site served by ActivityRelay, or will it always be stuck showing a 404 error? It would be good to display even simple information at the root. |
A good example of this is Yukimochi's own relay. The URL https://relay.toot.yukimochi.jp/ serves an information page, but the endpoints are at https://relay.toot.yukimochi.jp/inbox and https://relay.toot.yukimochi.jp/actor. Is the information page being served by the relay software, or using some sort of redirect in the web server? |
I thought it might be possible to have specific proxy_pass clauses for /actor and /inbox which pass through to the relay, and a separate one for / serving static content. I might have malformed the nginx directives here, but / is still intercepted by the relay and shows a '404 not found' when serving an index.html file. Interestingly, if no file is there I get a standard nginx '403 Forbidden' page.
|
Fixed! If I use the following then I can serve an index.html file from the /var/lib/relay folder (where my config.yml lives), with the endpoints also functioning correctly.
|
Hi @rodti whenever I use this I get a 502 error during the proxy pass. Did you see that happening on your end? |
For anyone else using the docker version of this relay, you have to do a bit more setup in the docker-compose file and in the nginx conf. Here's what my updated docker-compose looks like: as you can see I gave my server container the name "relay" this will be used later in the nginx file
For the nginx config we need to set and upstream for our proxy config to listen to that relay container's port 8080
|
I have this in my nginx config to serve index.html if only the root path is specified:
|
The relay seems to be working, the logs and the test I ran in my instance seem to support that, however I don't see any page that shows who is in the relay and furthermore where I attempt to connect to the listening port it just returns a plain "404 page not found", it doesn't respect the icon or anything "cosmetic" I set up. Is that even included?
For what I saw in your page I assumed it was going to look like that roughly, is there no http server that shows the instances connected to the relay?
The text was updated successfully, but these errors were encountered: