I am just wondering what I need to do and what the risks are in making my BrewPi accessible remotely from work, on holiday etc.
My BrewPi is connected wirelessly to my home LAN with many other PC’s and devices on it. I am assuming all I would need to do is configure my router to forward the port to the static IP address of my BrewPi set up? The router is one of the VirginMedia superhub cable jobbies.
My passwords are all stock etc at the moment. So I would need to change the password on the Raspberry Pi but is there anything else to do? Is it too risky?
I have mine opened up using port forwarding and then there are instructions on another forum http://www.homebrewtalk.com/showthread.php?t=466106&page=269 on how to create a separate page without the buttons (to stop unwelcome visitors from tweaking with your settings) this means that to make changes to the brewpi settings they would have to know your username and password.
It’s a fairly simple process just cutting and pasting the info from prymals post into some new files, but I’m sure if Brewpi updated something on the web interface this change could interfere with that. But for me it works.
I also got a free domain and mapped it to that so I don’t have to remember a long IP www.oldlarrybrewingco.tk
@Dean I share my BrewPi web interface over the internet, currently I only forward to the port of the web site which I have changed from the default, mine is on 8085 so I go to the site as follows. http://www.xxx.com:8085, I have password protected the whole apache server, but have come across this post http://www.homebrewtalk.com/showpost.php?p=6594822 which seems reasonable, you have a public read only pages, and a password for the admin (settings pages).
I got mine from www.dot.tk it was free and just allowed me to mask my IP address as for the password change the regular password through the RPI Config page use a secure password and you should be fine
I had to do a complete overhaul of my Pi (somehow my SD was corrupted) and finally got around to doing this. How great is this? Thanks @mikmonken for sharing this and his site.
Hey there @mikmonken, I was following those directions from the forum but am stuck on #3 where it says "Create a file with vi or nano called index.php and add the contents of the code block below (Mostly fixes in the Javascript section of the file) "
Could you explain how you create a file and add the contents?
So assuming your in the folder that step one points you and that you need to create the index.php file
type sudo nano index.php
This will then open up a blank window and I cut and paste all the contents from post 3 into that window and save and exit.
It’s easier to do these commands if you’ve connected to the pi via SSH as you can then just use the normal Mac or Windows shortcuts to cut and paste big blocks of text.
Oh man, thanks a ton! I just skipped the original post (page 9) and moved on to these more recent directions. That won’t mess it up either right?
Also, on the last part, “Create a file using vi editor called .htaccess and inside of it put
the following, modify the first line where it is bold and replace it
with what you plan to call your Private PHP file. Do you just rename the first line (“admin.php”) to anything specific?” And do you do anything with the “YOUR LOGIN HERE”?
Thanks bud
Sorry for all the questions. I really don’t understand this stuff too well.
Yep the admin.php is the bit that allows you to login and edit for example to access and edit brewpi on my home network I put 10.0.1.7/admin.php I can’t remember what I put in for the login part though
Yep exactly, the user name I just kept as pi but I can’t remember if this was the user id for the pi of the htpassword but I think I kept the same user name anyway.
Man, thanks a ton for the help @mikmonken. I’m up and running. I just left everything the same on that last part (except for the IP address, obviously) and it all works quite nicely.
Dear folks (i.e. @mikmonken),
I have a couple of questions regarding this one in order to get it working, which I haven’t yet been able to find answers for. Can someone help provide some input here? In the 2nd section of Prymal’s post:
In step 5, do you need to replace “webmaster@localhost” (line 2) w/ anything else?
–> When I run apache2ctl -k graceful (per step 6-8), I get the following error:
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1. Set the ‘ServerName’ directive globally to suppress this message
–> I tried replacing [webmaster] w/ my new username and [localhost] w/ my RPi’s IP address and I get the same message when I try step 8. Also, [127.0.1.1] isn’t my RPi’s IP address lol
In step 10, none of it is bold? Which part does they mean when they say “modify the first line where it is bold and replace it with what you plan to call your Private PHP file”?
For step 5, just change “AllowOverride All” Making sure the “All” is there is the only thing you need to change. Leave the “webmaster@localhost” alone.
I’m not really sure what this means. Sorry.
It’s saying you can replace the “admin.php” to whatever you want to call it. I just left it as “admin.php” and it worked great. You do want to change the second-to-last line and replace that ip address with your RPi’s ip.
