Tailscale?

[fvdw]

nice,
About tailscale install, yes it is possible but the easiest way is to install it via the webinterface using the zip file provided.
The firmware will unpack the archive and install the files in the right place.
See this post https://plugout.net/viewtopic.php?f=27&t=3808&p=39407#p39387
Why would you want to do it differently? :scratch

[fun3883]

Well, the webserver is not starting, as per boot.log, so neither myself remotely nor my brother locally can http to the NAS.
The only possibility is to ssh to it.

If there are some other logs for the http server than the boot.log, then it might tell about the issue.
I checked in /var/log but could not see anything good info.

Any idea what I could try to start it?
Thanks!

[fvdw]

Ah clear. There is way to get more info.
On the command line give this command an after that reboot your nas.

Code: Select all

debugon

After the reboot the boot.log will be more detailed furthermore in /var/log you will find the sys log with more detailed info.

The zip I have posted can be exctracted and you will find an archive when extracted. Extract this archive and find another archive in there you will until find the files tailscale and tailscaled.
These two files must be put in the shared folder fvdw/addons/bin
(full path when connected with ssh /direct-usb/fvdw/addons/bin)
copy the files there and make them executable using chmod command (chmod 755 ...) I assume you are familiar with thes linux commands.

[fun3883]

Boot.log extract:

Code: Select all

mwexec()[2024/11/25 10:47:05]: sed -rie 's/(memory_limit =).*$/\1 8M/g' /etc/php.ini
mwexec()[2024/11/25 10:47:05]: sh -c 'echo  > "/etc/SSL_fvdwsl.conf"'
mwexec()[2024/11/25 10:47:05]: /usr/bin/httpd -f httpd.conf -d /etc
                                 [ Fail ]
 * Starting mount of internal USB ...
 * Finishing mount internal USB ...      [ OK ]


If I manually try to start it, with /usr/bin/httpd -f httpd.conf -d /etc
I receive message:

Code: Select all

(99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.5.1.2:80
no listening sockets available, shutting down
AH00015: Unable to open logs


10.5.1.2 is the IP of the local PPTP server (default IP when configuring it).
If I change the /etc/httpd.conf file, section "Listen" to match the IP from the LAN (192.168.1.3) and try to start again, I then get:

Code: Select all

(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs


I did not yet try the manual install of Tailscale.

Thanks for the ongoing support you provide :thumbup

PS: I made an additional donation, as I really appreciate your work!

[Jocko]

Hi

Why do you want to set an IP with the directive Listen ? You should set only on what port the web server is available

Code: Select all

(99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.5.1.2:80

That would mean the port 80 is already in use

[fvdw]

In addition to comment of Jocko. If you use the pptp server you don't need to adapt httpd.conf file.
The pptp server is a separate proces. When setting up a vpn connecting using pptp server just for instance using a windows pc fill in the ip address of your nas or ip address of the WAN site of your router in case you have forwarded the relevant ports to your NAS, fill in the username and password of the authorized user that you enabled in the vpn server leave domain blank.
If the connection succeeds you can use the vpn ip 10.5.1.2 to connect to your nas

[fun3883]

Hi

Why do you want to set an IP with the directive Listen ? You should set only on what port the web server is available

Code: Select all

(99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.5.1.2:80

That would mean the port 80 is already in use

Merci Jocko, j'ai commente la ligne Listen, et maintenant le serveur web demarre :)
Thank Jocko, I have commented the Listen statement and now webserver starts

[fun3883]

In addition to comment of Jocko. If you use the pptp server you don't need to adapt httpd.conf file.
The pptp server is a separate proces. When setting up a vpn connecting using pptp server just for instance using a windows pc fill in the ip address of your nas or ip address of the WAN site of your router in case you have forwarded the relevant ports to your NAS, fill in the username and password of the authorized user that you enabled in the vpn server leave domain blank.
If the connection succeeds you can use the vpn ip 10.5.1.2 to connect to your nas

As I wrote to Jocko, webserver now starts correctly!
Now, the PPTP tunnel tunnel is between the 2 NASes (2big2 and Syno), but there's no web browser in DSM. It seems there are possibilities to get 1, via docker, but the NAS being a J (ds215j) version it does not support docker.
So am not trying to build a 2nd PPTP tunnel, this time from one of my PC, but connection fails for the different attempts I tried.
I used the same settings as the working one on the Syno (MS-CHAP v2) with same credentials (as also found in chap-secrets file). but no way. :fists
I will try another possibility: SSH tunneling....
Default resort will be to call my brother and run screen sharing session for the Tailscale install :lmao

[fun3883]

Update: SSH tunnel worked, I was able to reach 2big2 web interface.
I installed tailscale and onboarded it.
I was then able to reach webinterface using the Tailscale IP of the 2big2.
I need now to test the rsync.
From my perspective we can close this thread!

Thank you for your excellent support Jocko and Fvdw :applause

[tinamar]

Jocko and Fvdw
Would it be possible to install Tailscail on Cloudbox white casing?
thanks.