Testing the legacyweb.net project; Use modern web on older software/hardware

[mactjaap]

I did the test on a Orange Pi One. Not sure if this is OK. But I have it at my desk. I do have a Raspberry Pi, but didn’t use it seriously.
 
To start I add a wireless USB dongle to the OrangePi, added a udev rule to get it known as wlan0
 
vi /etc/udev/rules.d/75-persistent-net.rules
with this in it:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:13:ef:c5:2d:40", NAME="wlan0"
Activated wlan0 with nmtui and ssh-ed to its ip address to check if everything is working ok. It was.
 
Then did the install. I needed these commands
 

 
apt-get update
apt-get install ansible
git clone https://github.com/justinschw/legacyweb.git
cd legacyweb
./runinstall.sh
 
root@orangepione:~/legacyweb# ./runinstall.sh
[DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and make sure become_method is 'sudo' (default). This feature will be removed in a
future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

PLAY ***************************************************************************

TASK [setup] *******************************************************************
ok: [127.0.0.1]

TASK [gateway : install dnsmasq] ***********************************************
changed: [127.0.0.1]

TASK [gateway : install redis server for hostname-page lookup] *****************
changed: [127.0.0.1]

TASK [gateway : install redis tools] *******************************************
ok: [127.0.0.1]

TASK [gateway : template] ******************************************************
changed: [127.0.0.1]

TASK [gateway : template] ******************************************************
changed: [127.0.0.1]

TASK [gateway : template] ******************************************************
changed: [127.0.0.1]

TASK [gateway : template] ******************************************************
changed: [127.0.0.1]

TASK [gateway : template] ******************************************************
changed: [127.0.0.1]

TASK [gateway : command] *******************************************************
changed: [127.0.0.1]

TASK [gateway : command] *******************************************************
changed: [127.0.0.1]

TASK [gateway : service] *******************************************************
changed: [127.0.0.1]

TASK [gateway : service] *******************************************************
ok: [127.0.0.1]

TASK ************************************************
changed: [127.0.0.1]

TASK mailto:: install stunnel4 *************************************************
mailto:: install stunnel4changed: [127.0.0.1]

mailto:: install stunnel4TASK mailto:: install stunnel4mailto:: install postfix ********************************************************
mailto:: install stunnel4mailto:: install postfixchanged: [127.0.0.1]

mailto:: install stunnel4mailto:: install postfixTASK mailto:: install stunnel4mailto:: install postfixmailto:: template ********************************************************
mailto:: install stunnel4mailto:: install postfixmailto:: templatechanged: [127.0.0.1]

mailto:: install stunnel4mailto:: install postfixmailto:: templateTASK mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template *********************************************************
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templatefatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "msg": "Job for stunnel4.service failed because the control process exited with error code. See \"systemctl status stunnel4.service\" and \"journalctl -xe\" for details.\n"}

mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templatePLAY RECAP *********************************************************************
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template127.0.0.1 : ok=17 changed=14 unreachable=0 failed=1

mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templateInstalation is OK, only stunnel failes, but that is only needed for email i guess.
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templateWlan0 seems to have losts it’s ip address. Nmtui doesn’t get it back. 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templateThis is not Ok because the Pi doesn’t have an connection to the internet anymore. Not sure why this happens.
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templateI decide to hook up an old computer. A Windows XP notebook is most simple (sorry).
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templateNo go. I did get correct IP information, but cannot connect with a web browser to the IP address of dns name legacyweb.net.
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 

mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 

mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: template 
mailto:: install stunnel4mailto:: install postfixmailto:: templatemailto:: templateI will try to debug, but I think it is nice to show this outcome first.

 

[mactjaap]

I noticed I lost wlan0 network connection. So I revived it bij entering ssid and password in /etc/network/interfaces. WORKS!

But for now I'm stuck. Should there be a web server running? Firewall? is stunnel4 improtant? I wait and see if I get some help in this topic. 

 

[agent_js03]

Hi mactjaap, thanks for testing this. I also had tested it recently on my raspberry pi and found the same thing. Sorry it has been taking so long to respond, I am a family man and don't have a whole lot of time these days with my second little one coming soon...

I have an explanation why everything doesn't work out of the box. Basically I had been developing everything in a virtualbox vm running (what I believed to be) the same version of debian that was running on the raspberry pi. But apparently the versions were quite different between raspbian repos and the main debian release, and these differences were apparently significant enough to break legacyweb.

I have a lot of changes I made manually on the pi and wanted to upload them to the git repo. When I have the time I will do this and it should fix things.

To answer your questions, yes there should be an apache server running, and stunnel is necessary if you want email.

Can you type: systemctl status stunnel4.service

and also: journalctl -xe

I forget what exactly goes wrong with stunnel. I know it has to do with the configuration file... I can tell you exactly what to type in.

 

[mactjaap]

Ok. I wait for you upload your changes to GitHub.

First I would like to test the Web capabilities. I have not much interest in stunnel. But nice if it works for other people.