@NeoLoger I got my start in I.T. seven days after the IBM PC came out. I actually worked on the ARPAnet at the Pentagon before the Internet was available.
As they say, "you can lead a horse to water, but you can't make him drink".
2 Likes
Is your wi-fi zone hidden (no broadcast)? The extra key/value pairs in the network paragraph are in question.
Unfortunately, you haven't indicated what happens after this paragraph. I'd suggest copying/pasting what I have here to replace your entire file contents. It's from my own troubleshooter tool.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US
network={
scan_ssid=1 # Use this only if your zone is hidden, otherwise omit entire line
ssid="insert_your_hidden_SSID_here"
psk="insert_your_wifi_password_here"
key_mgmt=WPA-PSK
}
I'll give this a shot and let you know. Though after playing around in VirtualBox with the RaspianDesktop2017-11(32Bit).VDI File Image. I did notice that to get the Raspberry Pi 3 B+ to work with WIFI, I had to go into the Preferences Folder and under Networking actually highlight the SSH Icon. The other thing I did happen to notice though is that even after installing OctoPrint in a Raspian Environment. There is no easy way to bring it forth onto the screen of the Raspberry.
@rockman44181000 OctoPrint is a web service, among other things. If you want to see the web interface, you have to visit it with a browser.
Assuming that you have a screen permanently connected to your Raspberry, you could run the sudo ~/scripts/install-desktop script to add the PIXEL/Desktop GUI, install Chromium and then bring up the web interface locally on the Raspberry.
1 Like
Look I am sorry if i offended you, i just I got really frustrated with this problem.
I was wreaking my brain on this for several days and wasted more than one weekend to figure it out.
My day job is a System Engineer and i spend 10+ hours a day configuring Linux server on the cloud for costumiers and fixing problem, I'm literally breathing Linux, configuring a network interface is one of the most basic thing i do every day.
Any way, apparently there might be something wrong with the WiFi chip of my raspberry/raspberry model
I can see the networks but no matter what i do it wont connect, I tried using external USB network adapters i had laying around and they didn't work ether(maybe Linux compatibility issue i didn't checked).
Eventually I gave up on trying to fix the WiFi that comes builtin and after some research I purchased
A new USB WiFi network adapter TL-WN725N as soon i plugged it to my raspberry it instantly connected to my home network without any additional configurations.
I'm suggesting to consider adding this as a last resort solution to the WiFi problem.
Because i still have no idea why the builtin WiFi chip won't connect as it seems it can detect the router's WiFi signal perfectly.
I get it. You still don't believe me. But I'm right on this account.
The PacBell guy who arrived in my datacenter (as in "I owned and operated my own datacenter") similarly issued me a network range which wasn't kosher. He also gave me the "I'm the expert here" speech. I had to spend a good thirty minutes of my time on the whiteboard teaching him at the binary level how netmasks are applied.
To determine the number of subnets, use the 2x-2, where the x exponent is the number of subnet bits in the mask.
That "-2" part of the equation means that you need to throw away two subnets since they can't be used. This means that 10.0.0.0/24 is an invalid network. The first valid network is 10.0.1.0/24.
2 Likes
I've tried that script as well as a few others and I still can't get OctoPrint to appear in the Chromium Web Browser. Even though if I ls -h in the Root Directory I can see OctoPrint and all of its Files. I'm now trying the Budgie Desktop and any others that seem like they might work.
It would be interesting to figure out what was actually changed in the Raspbian Desktop when OctoPrint was Incorporated into it. Unlike the OctoPrint Download 15.01, the Raspbian Download didn't require any effort on myself to modify the octopi-wpa-supplicant.txt file.
I tried that too and now to top it all off. My Raspberry can't be seen by my network. Wired or Wireless. Go Figure.
I note that I've installed more Raspbian and OctoPi images than I can remember. I wrote a database program and I put tiny labels on the microSD and their respective SD adapters. I'm now up to 164 as an ID tag for the last one I did today.
- I follow the basic instructions on the OctoPi repository. I always use Etcher. I note that in some cases (like in Windows) it tries to unzip the file it downloaded but this is not preferable, let Etcher have the zip version.
- My network has both 2.4Ghz and 5Ghz zones (I only have a Raspi3B and Zero's which only support 2.4Ghz). My zone displays on devices like an iPhone wi-fi connect page (it's not hidden).
- I edit the
/boot/octopi-wpa-supplicant.txtin each case. - I boot them up and they always connect unless I've made some typo.
And by "they work", I mean that since I do so many of these I have to edit my workstation's ~/.ssh/known_hosts file to remove the last "octopi" or "raspberrypi" entry.
I might put a monitor/keyboard/mouse onto the Raspi to see what happens when it boots. You can then do an ifconfig locally to see if anything binds to either adapter. When you suggest that Ethernet isn't working then you'd need to go this route. It's possible that it's not even booting.
As discussed earlier in this thread, on my router I make sure that I've issued a valid network address like 10.10.10.0/24, for example.
Interpret the LEDs on the Raspi and see what it's trying to tell you.
1 Like
Upon power up my RPI based Octopi works fine and has no WIFI connectivity issues......but after 2-3 days, while it shows in the router as connected, no local host on its subnet can ping it, much less connect....it takes a power cycle on the RPI and its back operational...
its a straightforward classic install of Octopi on the RPI with no deviations or changes....
its almost like its related to the renewal of the router's DHCP lease to the Octopi, although I cant tell what that period is, but its repeatable like clockwork...like it renews but loses IP routing connectivity....no other issues on the network...
any suggestions?
I'm using the Pi Model 3 B, flashed octopi-stretch-lite-0.15.1 to a 32GB microSD with Etcher, can't seem to get it to connect. It gets stuck at line " random: crng init done", not sure if this is supposed to happen...
What I've tried (basically everything from the troubleshoot):
-
flash using Win32DiskImager
-
using a different microSD card
-
using 5V 3A power adapter
-
using Notepad++, also Atom text editor
-
checking router's set-up/control page, Angry IP Scanner
-
connecting Pi through an ethernet cable (with the following octopi-wpa-supplicant.txt, not sure if I'm supposed to comment out the wifi settings when using ethernet?), but still don't see it under "connected devices" on router's set-up/control page.
Other info:
-No, I don't have a hidden SSID.
-Yes, it's on 2.4G, not 5G.
-Yes, I have good Wifi reception and the Wifi module is working. Installed NOOBS previously to confirm. Was able to see it under "connected devices" on router's set-up/control page.
-Yes, I'm Canadian. 
My octopi-wpa-supplicant.txt:
# Use this file to configure your wifi connection(s).
#
# Just uncomment the lines prefixed with a single # of the configuration
# that matches your wifi setup and fill in SSID and passphrase.
#
# You can configure multiple wifi connections by adding more 'network'
# blocks.
#
# See https://linux.die.net/man/5/wpa_supplicant.conf
# (or 'man -s 5 wpa_supplicant.conf') for advanced options going beyond
# the examples provided below (e.g. various WPA Enterprise setups).
#
# !!!!! HEADS-UP WINDOWS USERS !!!!!
#
# Do not use Wordpad for editing this file, it will mangle it and your
# configuration won't work. Use a proper text editor instead.
# Recommended: Notepad++, VSCode, Atom, SublimeText.
#
# !!!!! HEADS-UP MACOSX USERS !!!!!
#
# If you use Textedit to edit this file make sure to use "plain text format"
# and "disable smart quotes" in "Textedit > Preferences", otherwise Textedit
# will use none-compatible characters and your network configuration won't
# work!
## WPA/WPA2 secured
network={
ssid="Ken2.4G"
psk="7788792238"
}
## Open/unsecured
#network={
# ssid="put SSID here"
# key_mgmt=NONE
#}
## WEP "secured"
##
## WEP can be cracked within minutes. If your network is still relying on this
## encryption scheme you should seriously consider to update your network ASAP.
#network={
# ssid="put SSID here"
# key_mgmt=NONE
# wep_key0="put password here"
# wep_tx_keyidx=0
#}
# Uncomment the country your Pi is in to activate Wifi in RaspberryPi 3 B+ and above
# For full list see: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2
#country=GB # United Kingdom
country=CA # Canada
#country=DE # Germany
#country=FR # France
#country=US # United States
### You should not have to change the lines below #####################
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
Photo of when it boots (with only HDMI connected, no ethernet or anything):
It's my first time using Raspberry Pi, a complete newbie. I might be missing something obvious, please have patience.
The default DHCP lease is often a day. Feel free to go into your network router and adjust this to three weeks.
Also, you didn't mention which workstation operating system you're using (Windows, OSX, Linux). OctoPi broadcasts its hostname best on Bonjour, for what it's worth. So if you installed that service on Windows it might behave better.
Its windows8.1....It's not a hostname issue...I try to ping directly with its ip address....shows leased and connected on the wifi subnet with that ip in the router, but wont answer ping or broadcast ping (arp -a) after a few days....am now going to have it crontab reboot every night at midnight and see if the problem disappears since rebooting it allows it to communicate again on the subnet...this happens on RPIOW and RPI3b+ that I have using the standard Octopi image installed per instructions...
I followed these.. OctoPrint.org - Download & Setup OctoPrint .dont see any significant differences in the install instructions...
OH MY GOD! THANK YOU! THAT FIXED IT!!! I thought I'd have to wait days for a response ;-;;
Couple things the guide did differently (For those who run into this same problem in the future @hwurzburg ):
-
Download directly using "curl" through command prompt.
-
Install Bonjour.
-
Burn the .zip file directly, not the .img file inside. (This is actually a lot faster too!)
-
include "key_mgmt=WPA-PSK" in the octopi-wpa-supplicant.txt (I don't think this is what fixed it, but hey it's working
)
1 Like
@xKen The new problem is that some of these browsers or operating systems want to try to help you by automatically unzipping the download and end up tweaking something.
1 Like
Windows is affected by not only the DHCP server's lease (if it's trying to find octopi.local) but it's also affected by its own arp cache, for what it's worth. The arp cache empties out after some amount of time which nobody knows other than the geek who wrote that document.
Somehow this feels more like a router-based problem than it does your Raspberry. If it were me, I'd wait until the problem shows up again (having put a keyboard/monitor/mouse on the Raspberry) and then run an ifconfig locally on the Pi to see if the wlan0 has its RUNNING flag.
Greetings,
I am having an interesting problem with getting OctoPi to work with my Raspberry Pi 3. Before, I followed the exact steps of everything (flashing to a freshly wiped microSD card, editing the wpa file properly with Notepad++, putting in microSD card before using a wall outlet power supply to turn it on) and it worked instantly at school. However, now that I am home the octoprint is not showing up at all. I have changed the
- Changed the wpa text using Notepad++
- Wiped the microsd card and reflashed it
- Confirmed with my home internet that octoprint was indeed connected (still got nothing from the octoprint.local)
- Used a different microsd card
- Used an entirely different router that I had used and worked at school (still no good)
- Plugging in an HDMI does nothing (I assumed it was suppose to let me edit it/check that it works) so I don't think I can get diagnostic info atm...
- There is a solid red LED. A green led flashes every now and then (no pattern it seems)
So its my understanding that the raspberry pi is working and connected, but I can't access it from the outside. Very sad/annoyed because it was perfect the first time but now not working at all 
anyone have advice?