I followed this guide to set up a Matrix server on my Pi. The only hiccup I ran into during setup was under “Setting up Synapse server,” step 11, the “Registration” section wasn’t present in homeserver.yaml. This server is meant to just run bridges to WhatsApp/Facebook/etc. so I wasn’t too worried, and forged ahead.
I’m getting the title error when trying to connect via Element. Federation Tester gives the following error:
Get “https://[my ipv6 address]:8448/_matrix/key/v2/server”: dial tcp [my ipv6 address]:8448: i/o timeout (Client.Timeout exceeded while awaiting headers)
Check your proxy’s CORS origin statements and make sure they align with the recommended config for your brand of proxy (nginx, caddy, etc.) I had a similar issue with mine and that solved it. Consult your doctor if your proxy can’t stay running longer than four hours.
I appreciate the help but unfortunately have no idea how to do that. Before this, my only real experience was Plex on Windows and light desktop usage on Linux, so I’m pretty green.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Check your proxy’s CORS origin statements and make sure they align with the recommended config for your brand of proxy (nginx, caddy, etc.) I had a similar issue with mine and that solved it. Consult your doctor if your proxy can’t stay running longer than four hours.
I appreciate the help but unfortunately have no idea how to do that. Before this, my only real experience was Plex on Windows and light desktop usage on Linux, so I’m pretty green.
I did configure nginx in the tutorial.
@Zoidsberg Are you using ipv6 address as homeserver hostname?
I am not, no.