MakerGear Forum

Hello all,
I had octoprint working last week just fine. I changed my wireless router ssid and password a few days ago. I connected my raspi up to my monitor and keyboard and went into the wifi config tool and connected exactly like I did last time but now it keeps scanning, doing a 4-way handshake and repeating!
I turned it off and started from scratch! I formatted the SD card, put the octopi image on there and it is still doing the exact same thing!
I have no idea what to do now!

I could really use some help on this!
Thanks guys.
Brandon

Edit: Also.... everytime I try to go to octopi.local it just goes to a search page or says not found.... is the server down?

Ok..... I always find my own answer and fix my own problem right after I start a thread!!!! always happens that way not matter how much research I do beforehand!

I am going to leave this here just in case it helps someone else out. It was hard to find for me.

Ok, #1.... Do not use special characters for your wifi password... That is what was tripping my raspi up. There is a way you can do it, but it is beyond me.

#2 Your printer has to be hooked up to your raspi and turned on for octopi.local to work.....

Now what if I want to connect from another network... OH BOY!

Ok, One last thing and I will leave you guys alone... I am able to get onto the octopi.local from my laptop. I cannot open the page on my desktop. I tried chrome, IE, and Firefox. I am out of ideas....
Also, Since I don't have the raspi hooked up to a screen or keyboard. is it safe just to unplug it when I don't plan on using it for awhile?

Try connecting directly to the IP of the pi, rather than http://octopi.local

At a guess, however the name resolution stuff works, it doesn't translate across the different network interfaces on the router (wifi/ethernet) properly.
I've seen similar problems, where it'll only work from some machines, but not others. But IP's always work.
Set up a static DNS lease on your router helps avoid it randomly changing on you.

To connect identically from outside your LAN as from inside, you need to use a static IP address, port forward through your router, set up external DNS, and enable hairpin routing. Only the first three steps are necessary, the last two are optional. How that is done depends heavily on your router.

For the first one, you can use a static lease as benavery suggested. Select a unique port for OctoPrint, such as 5000, and have your router forward that port to the static IP your RaspPi is on. You can then reach it by using your external IP address and that port: http://x.x.x.x:5000/. If you want to use a hostname, I like duckdns.org as it is free and easy to set up within many routers that support such services. Finally, if you want to reach it as http://yourservername.com:5000/ from inside your network as well as outside, you will generally need to enable something called hairpin NAT. How that is done varies depending on the router, and may not be possible.

Raspberry Pi runs a full Linux operating system, and you generally don't want to just kill power to it as it may corrupt the filesystem, although with modern journalling filesystems today that is less of a worry. I would try to shut it down gracefully before unplugging it (sudo shutdown -h now).

Sorry I haven't replied lately. Been trying to do research on getting a static IP address and everything, there is a ton of info out there but this is all fairly new to me. I know I can figure it out but it will just take some time. It almost seems like too much trouble for what I really want to do, which is just being able to observe my printer and shut it down remotely if I see a print going wrong. I don't plan to leave the printer running on its own too often but it is helpful on those long prints when you have to run to the store or something.
I could just buy another security camera for $30 and put my remote power outlet on the printer then I could view it and shut it down from my phone if I had too.
Would pulling the plug hurt anything if I had to stop a print remotely?

I like the idea of the raspberry pi and octoprint but at the moment it needs more research on my part that I just don't have time for right now.

Thanks again for all the help guys!
Brandon

You may be able to set up a dynamic DNS updater like duckdns instead of going through the trouble of getting an external static IP. It automatically assigns your current IP address to a DNS name so you can always reach it. Check your router settings for such an option.

For a possibly easier to use option, check out AstroPrint. I've seen multiple mentions of it recently after never having heard of it before. It's apparently a fork of octoprint that has been reskinned and has some additions to make it easier to set up and use remotely.

I checked out astroprint, it does look like a nice streamlined solution but it costs about $140 and has a $10 a month fee. I don't want to admit to how non-computer savvy I am but..... duckdns might even be over my head. I know what you guys are thinking "why on earth does this guy even own a 3D printer?" and to that I say "I like a challenge!"

I will eventually figure it out! Thanks again for all the advice guys.

You don't need to buy their box, you can download an image for the Raspberry Pi to do the same thing: https://learn.adafruit.com/astroprint-3 ... g/software
And the $10 month subscription to their online service only seems to apply if you are connecting more than one printer, although it is devilishly hard to find out anything on their web site without signing up first.

jsc wrote:You may be able to set up a dynamic DNS updater like duckdns instead of going through the trouble of getting an external static IP. It automatically assigns your current IP address to a DNS name so you can always reach it. Check your router settings for such an option.

For a possibly easier to use option, check out AstroPrint. I've seen multiple mentions of it recently after never having heard of it before. It's apparently a fork of octoprint that has been reskinned and has some additions to make it easier to set up and use remotely.

Dyndns is another option. I had problems with my modem not properly updating when my IP changed, but dyndns has an updater you can run from your computer to do the same thing. Dyndns isn't free anymore, though.