[GH-ISSUE #14] local HTTPS sites not working from VPN #15

Closed
opened 2026-03-02 07:11:03 +03:00 by kerem · 2 comments
Owner

Originally created by @quinnsam on GitHub (Nov 11, 2016).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/14

After connecting to the VPN (xauth) I am not able to load my local https websites. I am able to connect to regular http websites located by the docker host but not https. While connected to the VPN I am able to ping the docker host with no problems. I have also added exceptions to the firewall on the host for the website port as well as 443 for SSL, with no luck.

I receive the following error: ERR_ADDRESS_UNREACHABLE

I also attempted to use the --net=host but receive error:
xl2tpd[1]: setsockopt recvref[30]: Protocol not available
xl2tpd[1]: This binary does not support kernel L2TP.

Is this something that I should change in the Dockerfile or is this a host error?

Originally created by @quinnsam on GitHub (Nov 11, 2016). Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/14 After connecting to the VPN (xauth) I am not able to load my local https websites. I am able to connect to regular http websites located by the docker host but not https. While connected to the VPN I am able to ping the docker host with no problems. I have also added exceptions to the firewall on the host for the website port as well as 443 for SSL, with no luck. I receive the following error: ERR_ADDRESS_UNREACHABLE I also attempted to use the --net=host but receive error: xl2tpd[1]: setsockopt recvref[30]: Protocol not available xl2tpd[1]: This binary does not support kernel L2TP. Is this something that I should change in the Dockerfile or is this a host error?
kerem closed this issue 2026-03-02 07:11:04 +03:00
Author
Owner

@hwdsl2 commented on GitHub (Nov 11, 2016):

@quinnsam Hello! This output is normal:

xl2tpd[1]: setsockopt recvref[30]: Protocol not available
xl2tpd[1]: This binary does not support kernel L2TP.

You may use "--net=host" but I don't think it is related to this issue.

Is your VPN client Android 6.0 or 7.0? If so, please see [1]. Also can you try rebooting your VPN client and/or VPN server?

[1] https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#android-6-and-7

<!-- gh-comment-id:260072284 --> @hwdsl2 commented on GitHub (Nov 11, 2016): @quinnsam Hello! This output is normal: ``` xl2tpd[1]: setsockopt recvref[30]: Protocol not available xl2tpd[1]: This binary does not support kernel L2TP. ``` You may use "--net=host" but I don't think it is related to this issue. Is your VPN client Android 6.0 or 7.0? If so, please see [1]. Also can you try rebooting your VPN client and/or VPN server? [1] https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#android-6-and-7
Author
Owner

@quinnsam commented on GitHub (Nov 11, 2016):

Unfortunately, in Android 7.1.1 there is no option for "Backwards compatible mode". And the "sha2-truncbug=yes" line was already present. I did solve the issue by switching from XAuth to L2TP.

<!-- gh-comment-id:260078308 --> @quinnsam commented on GitHub (Nov 11, 2016): Unfortunately, in Android 7.1.1 there is no option for "Backwards compatible mode". And the "sha2-truncbug=yes" line was already present. I did solve the issue by switching from XAuth to L2TP.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-ipsec-vpn-server#15
No description provided.