Skip to main content


Unhelpful error message - suggest IPv6 test?


!Friendica Support

Hi folks,

I was a bit baffled by an error from friendica (which appeared to otherwise be working), complaining that .well-known/host-meta was not accessible, and that this was a "severe" problem.

BUT - clicking the link in the error resulted in seeing the host-meta downloaded.

After a bit of head scratching (I've recently moved to nginx), I figured it out.

My local internet has only IPv4 connectivity - so it worked. My nginx was misconfigured, and has been ignoring requests on IPv6.

Can I suggest that the Admin panel add an additional test for ip4 and ip6 connectivity, so that admins can be warned?

Additionally, the message about host-meta might be reworded to include a hint to check IP6 connectivity or something.

TTFN, have fun folks,

-Ian

reshared this

Your system cannot access your system from itself.
yes, but the error isnt terribly helpful about that. the machine has ip6 and o does the dns - but the webserver wasnt configured properly, so the test for the host-meta file failed, but downloading it or trying to see why was confounded by the error not being visible from an ipv4 *only* client.

Friendica Support reshared this.

Content warning: Unhelpful error message - suggest IPv6 test?

Content warning: Unhelpful error message - suggest IPv6 test?

Friendica Support reshared this.

@Ian Molton This feels a little too low-level an issue for Friendica to warn admins about.

I’m not even even sure we have information from the PHP script to even show the relevant warning message.

I think it would be possible @Hypolite Petovan to get the DNS record of the baseurl and then do something with that information. And getting this information into the admin panel might be a niceexercise as it is separated from the complexity of most Friendica features.
@Tobias We can check whether there's both an IPv4 and an IPv6 addresses attached to a given domain but I don't think we can test further. We need to perform an HTTP request based on the domain, not based on the IP address, because of virtual hosts.

I think just adding a comment to the existing error message like

"this error may be caused by incorrect DNS configuration, lack of ipv4 or 6 connectivity, or take to enable ipv6 on the webserver"

Would be sufficient. A DNS check would be a nice addition though.

Friendica Support reshared this.

@Ian Molton @Tobias We can definitely update the error message.

*shrug*

Caught me out.

Friendica Support reshared this.

⇧