What is the problem?
When I try to access the plugin manager, it says "Repository is not available.
What did you already try to solve it?
Following numerous different threads on here and on google. Have restarted router and pi. Disabled "connectivity check", Reflash of the SD card and start over.
Logs (syslog, dmesg, ... no logs, no support)
New to a lot of this. How do I get my logs, which logs are needed.
Additional information about your network (Hardware you are trying to connect to, hardware you are trying to connect from, router, access point, used operating systems, ...)
Had to change the host ip in settings-server to 192.168.1.1 just to pass the test host and port. I can access octopi from my laptop, when connected to my printer I can control it. Have not tried sending a print to the printer yet.
Running octoprint 1.5.2 and Octopi 0.18.0 Rpi4, hooked up to a monitor with keyboard/mouse.
There's a logging panel in the settings. Logs is also a link, it you want to find out more. The octoprint.log is a good one.
What you have done here is basically disabled the point of a connectivity check. You have asked it to try and connect to your home network/router, which of course is already is because you're looking at the UI locally. This should be an external IP, the default is 188.8.131.52 which is cloudfares's DNS server.
Make sure you don't have firewalls etc. on the network that may be blocking it. Make sure your router does not block external access for some devices. You are looking for something that is stopping it accessing the outside world, try SSH and try pinging your favourite websites.
The octoprint.log should help to identify a possible cause.
octoprint (1).log (264.3 KB)
When I change the host ip to anything, even the default 184.108.40.206, It says the server is un-reachable
I can ping any webstie just fine through the pi.
So you can run something like
ping 220.127.116.11:53 or
ping 18.104.22.168:53 from the Pi, but the same thing does not work from OctoPrint. Interesting
If i try to ping 22.214.171.124, It works, but if i try 126.96.36.199:53, it doesnt
188.8.131.52:53 results with "name or service not known:
Hmm, same for me actually on the Pi, but the connectivity check works. Not sure it is a ping-able port then, just one that can be connected to as a test.
If you are on the command line, try this:
You should get a printout of the plugin repository.
curl: (7) Failed to connect to plugins.octoprint.org port 443: Connection timed out
from the commandline try ping www.google.com
if it comes up as unknown host, your router is either not giving the pi a DNS server to use, or you have messed with something in the network setup that is keeping it from using the DNS server
pi@octopi:~ $ ping google.com
PING google.com (184.108.40.206) 56(84) bytes of data.
64 bytes from ord37s03-in-f14.1e100.net (220.127.116.11): icmp_seq=1 ttl=119 time=17.9 ms
64 bytes from ord37s03-in-f14.1e100.net (18.104.22.168): icmp_seq=2 ttl=119 time=16.10 ms
64 bytes from ord37s03-in-f14.1e100.net (22.214.171.124): icmp_seq=3 ttl=119 time=16.4 ms
64 bytes from ord37s03-in-f14.1e100.net (126.96.36.199): icmp_seq=4 ttl=119 time=17.0 ms
64 bytes from ord37s03-in-f14.1e100.net (188.8.131.52): icmp_seq=5 ttl=119 time=17.2 ms
--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 9ms
rtt min/avg/max/mdev = 16.373/17.105/17.941/0.529 ms
There's no such thing as a pingable port, only a pingable host. Pinging is sending an ICMP packet to a host. What OctoPrint does is actually opening a socket connection to a host and port, not a ping.
If you want to check internet connectivity from the commandline, pinging a host (e.g.
ping 184.108.40.206 or
ping 220.127.116.11) is the way to go. To test name resolution, ping a hostname (e.g.
So it can reach the internet, it can resolve the host, but it can't establish a connection.
What do I need to do to be able to establish a connection? I've been fighting this issue for a week now. It's driving me insane.
It can be a multitude of factors. What I can tell you is that the page is up and running just fine, so it's not a general problem.
Can you reach plugins.octoprint.org from other computers on the same network? Does
date on the Pi show the current date and time? What about
pi@octopi:~ $ curl https://octoprint.org
curl: (7) Failed to connect to octoprint.org port 443: Connection timed out
pi@octopi:~ $ curl http://google.com
curl: (7) Failed to connect to google.com port 80: Connection timed out
General network issue then, nothing OctoPrint can fix.