Sorry but I’m not sure. Every time I’ve used that tool the setup has gone flawlessly. The first time you use it you put in your instance URL and it should output something for you to add to your DNS records. If you just made the DNS changes it can take a few minutes to several hours for those changes to be pushed out.
uhdeuidheuidhed@thelemmy.club 5 days ago
Thank you. I think I figured it out.
In my lemmy.hjson file, I accidentally put the internal IP address of my server instead of the domain name. This was a carry-over from testing on my main machine by using an IP address and port forwarding because I didn’t have a domain name to use.
I changed the
hostnamesetting in lemmy.hjson to my domain name, and now it seems to be working. Sort of.Now I have a different error, “Your instance is not guaranteed in Fediseer. Please check fediseer.com”, but this one seems less of a technical issue. I will have to learn what this is about and hopefully I can get it to work :)
FrostyTrichs@crazypeople.online 5 days ago
You’ll have to claim your instance on fediseer and have another instance endorse yours. It’s a system of trust to help keep bad actors from having too much influence over the platform and causing others grief.
uhdeuidheuidhed@thelemmy.club 5 days ago
Thanks yet again.
I tried claiming my instance, but now I’m getting the error:
API Key PM failedSlowly and steadily, this problem will be solved!
FrostyTrichs@crazypeople.online 5 days ago
IIRC the way it works is by PMing you the API key to get started and you’re failing at that point. Are you sure your instance is federating? I don’t know anything about how fediseer works on the backend but if it’s not able to send you a PM that suggests you might not be federating at all or maybe you’re running a whitelist or something? I’d start investigating if your instance is reachable from other instances and if you’re able to send yourself a PM from another instance.