i just built an image from download of OctoPi 0.17.0 on a rpi 4/4G and plugin manager is not working. i only get the default plugin in the list, does not show what is in the list at http://plugins.octoprint.org/
What did you already try to solve it?
searched forum. also tried to install a plugin manually and that seams to work
Have you tried running in safe mode?
yes
Did running in safe mode solve the problem?
same, no plugins from plugin url
Complete Logs
octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
octoprint 1.5.2, octopi 0.17.0, anet a8, stock firmware, raspberry pi4/4g. image from download
I believe your RPi can't access the internet due, most likely, by a failure to find a suitable DNS server (see below).
The log you posted is full of various network related failures but since you have OctoPrint 1.5.2, the network must have worked at some point in the past long enough for it to be downloaded (it
isn't included in the OctoPi 0.17.0 distribution).
Can you login to the RPi over SSH? If so, lets start with posting the output of: ifconfig, iwconfig, and cat /etc/resolv.conf. Please use the </> button in your reply so the output is readable.
2020-12-26 01:59:01,171 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity state is currently: offline
2020-12-26 01:59:01,172 - octoprint.util.connectivity.connectivity_checker - INFO - Connecting to 8.8.8.8:53 is working
2020-12-26 01:59:01,173 - octoprint.util.connectivity.connectivity_checker - INFO - Resolving am8p4.isgrop01.com is not working
I'm a bit confused about the apparent intermittent nature of this problem. Do you have anything like Pi-hole installed?
Since you are in a private network and your DNS servers are in (another) private network, we probably need more details about how your network is configured.
Also route, route -n, and traceroute 10.7.1.240 might be useful.
This is just the image download from the sight. Nothing added other than the one plugin to check to make sure I was not having connectivity issues.
There is a firewall between the two network. All policies are allowed from this device to the dns servers on the local network. The dns servers are Windows domain controller as well. Dhcp is done from the firewall/router. I’ll check all the policies between the two network. But as I said I installed octopod without any issues direct, since plug-in manager doesn’t work. I also tried using google for dns. There is an any any permit out to the internet. And that give no better results. The dhcp server has a reservation for this device, so same ip every time.
the firewall is permitting dns and ping to 10.7.1.240 and 10.7.1.244(Microsoft DNS servers)
pi@octopi:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.200.1 0.0.0.0 UG 202 0 0 eth0
192.168.200.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
pi@octopi:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.200.1 0.0.0.0 UG 202 0 0 eth0
192.168.200.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
pi@octopi:~$ ping 10.7.1.240
PING 10.7.1.240 (10.7.1.240) 56(84) bytes of data.
64 bytes from 10.7.1.240: icmp_seq=1 ttl=127 time=1.04 ms
^C
--- 10.7.1.240 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.039/1.039/1.039/0.000 ms
pi@octopi:~$ ping 10.7.1.244
PING 10.7.1.244 (10.7.1.244) 56(84) bytes of data.
64 bytes from 10.7.1.244: icmp_seq=1 ttl=127 time=1.51 ms
64 bytes from 10.7.1.244: icmp_seq=2 ttl=127 time=1.16 ms
^C
--- 10.7.1.244 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 1.156/1.331/1.507/0.179 ms
the network the Pi is on is my IoT network. it does not have access to my internal network, other than dns from my dns servers. these servers use forwarders poing to root servers on the Internet. and support my internal windows domain. there are other devices on the IoT network, these are all working. even my work laptop is on the 192.168.200.0/24 network. I don't think the issue is with the network, but with this Pi. I have octoprint on a pi0w currently running and was setting this up to replace the pi zero.
p.s.
as i said previously, i am able to install plugins, but need to do it manually and not through plugin manager. when i do it manually, it still reaches out to git to download the bits.
p.p.s
i am also getting notification of plugin update. but the plugins down show up in plugin manager.
In that case, maybe it is just name resolution of octoprint.org? I know it's hosted by GitHub however I don't know where the domain resolution would go first. The updates working implies github.com works fine.
Standard Raspbian distributions out of the box have a broken /etc/nsswitch.conf file. If you edit the file you will see a line like this :
Hosts: files mdms4_minimal [NOTFOUND=return] dns
Note the position of ‘dns’ after the NOTFOUND
This setting means DNS is never used.
Change the line to read
hosts: files dns mdns4_minimal [NOTFOUND=return]
Then dns will work. After a network restart.
One question - why is wired and wifi connected to the same network?
Read this set of posts for more info.
I’ve been running DNS services since 1990 and it’s still HARD.
i had wireless going first only because i came from a pi0w and then figured i could use wired and power the pi off of poe. ive since disconnected from the wireless. both wired and wireless use the same settings for dhcp and dns.
i think dns was working because i could ping using name on devices on the network that i had host records for. also ping host on the internet. ive been running 2 Internet facing name server since 1990 as well. pi's and linux are relatively new to me. the DNS BIND book is the reference book that i use for DNS
making the change in the nsswitch.conf did not resolve the issue. all other items seam to work. i really think there is something wrong with the plugin manager. wouldnt that setting be for mdns and not dns resolution? is there maybe a way to re-install the plugin manager? i also did a full update to get the pi hq camera working
on closer review of rcw88's recommendation, i see that i did not make the changes that were recommended. i have since made the change to /etc/nsswitch.conf and can not ping by host name to the Internet. this still has not resolved my plugin manager issue. but maybe a reboot after the change maybe needed.
when i go to setting-> server and test access to my dns server, i get server is reachable. but when i test name resolution, i get name can not be resolved. but when i ssh to the rpi and ping by hostname, i get name resolution.so it seams name resolution is not working in octoprint, but is working on the pi
update
the rpi does name resolution and has access to the internet. octoprint also does name resolution and has access to the internet. plugin manger is still broken. does not update the list of plugins past the default 18. this is after the change recommended by fcw88 and a reboot of the pi
Could you clarify this? I don't know of the default 18 you mention. If it can reach the repository it is either all or none, when you press 'get more' at the bottom.
Sounds like you are getting to the bottom of this, slowly but surely.
i left it alone and now when i click on get more, i can see the plugins now. woohoo. not sure what the deal, but must have been the nsswitch config issue and then time to refresh and clear some cache somewhere.
