Page 1 of 1

VPN functionality

Posted: 31 May 2023, 22:33
by sybarix
I've setup an OpenVPN server using my TNAS, and successfully managed to connect to it via the OpenVPN app on my Macbook by exporting the ovpn profile. I noticed several things do not work as expected:
1) My IP address does not change before and after connecting to the TNAS VPN.
2) I have enabled the option to "Allow clients to access the local area network where the server is located" as I thought it would enable my to connect to my apps via 192.168.xx.xx:xxxx from another network, but it doesn't work. Please let me know how to set this up.

Re: VPN functionality

Posted: 09 Aug 2023, 21:17
by XFNeo
{L_BUTTON_AT}sybarix

Hi! Have you tried a new version 2.0.49?
In release notes is mentioned that they fixed this option.

Re: VPN functionality

Posted: 10 Aug 2023, 18:08
by TMzethar
You can try changing to a different server specific static IP. If it works, you can try modifying it back to see if this is the main cause of the problem.

Re: VPN functionality

Posted: 16 Aug 2023, 05:30
by XFNeo
{L_BUTTON_AT}TMzethar
Hi! I have enabled "Allow clients to access the local area network where the server is located" on the latest version 2.0.49 and I cant connect to TOS UI via local address https://192.168.1.10:5443 but it works via https://172.10.11.1:5443

Re: VPN functionality

Posted: 23 Oct 2023, 18:24
by XFNeo
{L_BUTTON_AT}TMzethar
XFNeo wrote: 16 Aug 2023, 05:30 Hi! I have enabled "Allow clients to access the local area network where the server is located" on the latest version 2.0.49 and I cant connect to TOS UI via local address https://192.168.1.10:5443 but it works via https://172.10.11.1:5443
The problem is still relevant.

Re: VPN functionality

Posted: 14 May 2024, 23:50
by XFNeo
{L_BUTTON_AT}TMzethar
XFNeo wrote: 16 Aug 2023, 05:30 Hi! I have enabled "Allow clients to access the local area network where the server is located" on the latest version 2.0.49 and I cant connect to TOS UI via local address https://192.168.1.10:5443 but it works via https://172.10.11.1:5443
The problem is still relevant.