-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
Regularly stuck at "Initializing..." using web UI #282
Comments
FE80::/10 is reservated for local ip addresses in the ipv6 network. if you network use a different network, you have to add it. you can read more informations about FE80::/10 for example here: https://en.wikipedia.org/wiki/IPv6#Link-local_address |
From what I can tell, there is a larger "Unique Local Address" range defined for IPv6 that is subtly different than link local, but is equivalent to the non-publicly routable 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 ranges in IPv4: https://en.wikipedia.org/wiki/Unique_local_address My local network (using UniFi network gear) appears to be set up by default to allocate IPv6 addresses in the larger FC00::/7 range (outside of the link-local range). As a result, I get the above "Initializing..." hang / "unauthorized" errors. It seems like it should be universally safe to include the larger "Unique Local" range by default. |
Ah ok. I didn't know that. I will double check it in the team and maybe we will add it. |
I have a similar problem but without the
and i have a
adding the lines suggested by @esb7 seems to have fixed it (for now) |
If anyone is coming here because they are trying to use Tailscale to remotely connect to MainsailOS from within their tailnet, you will need to ensure that the ips of the connecting clients fall within the ranges defined in moonraker.conf's authorization.trusted_clients. Whether you use a range or verbatim ip address(es) is up to you (I personally just added the ip addresses of the devices I wanted to allow access). Perhaps this warrants an error message that makes it more clear that Moonraker says the client is unauthorized? |
I having same issue for different reason: I didn't have a non default ipv6 but this:
I have added this but no difference..
|
Updated since I'm still having the issue |
Solved my problem...thanks! Loving the Tailscale remote access. |
What happened
I regularly get stuck at "Initializing..." when accessing mainsail from a web browser on my Mac. Sometimes it works and other times it fails and will continue to fail even through reboots of the rPi hosting mainsail. It would occur on different web browsers as well.
What did you expect to happen
Web UI should be consistent and responsive, not hung.
How to reproduce
Use mainsailos.local to access the printer web UI.
Additional information
The issue seems caused by "unauthorized" errors that show up in the moonraker log:
I noticed that the failed authentications all had a reported ipv6 address and on further investigation were all in a range outside of the allowed range in the
trusted_clients:
section inmoonraker.conf
. The primary / default trusted ipv6 range isFE80::/10
. However that appear to exclude other local-only address ranges (including the FD70 my device had). I believe the default should be:FC00::/7
.For anybody that hits this, you can get past it by adding the following to the trusted clients: section of the moonraker.conf file:
The text was updated successfully, but these errors were encountered: