@debruina Once you make the connection, are you getting the same public IP as your network, if so, you are halfway there, I am thinking you have to forward a port on the 605 to access your web server. Are your network shares running on equipment with an ip addresses, if so you might have to also open a port to access those shares. meaning, to access your web server via an IP address you would have to include the IP:port number. 

  @debruina 

Can you open the local web server via local IP address? (through OpenVPN)

To me, it seems like a DNS issue, or NAT loop issue.

  @Somnus 

Somnus wrote

  @debruina 

Can you open the local web server via local IP address? (through OpenVPN)

 

To me, it seems like a DNS issue, or NAT loop issue.

No that doesn't work. Like i said I can ping it, but thats it. The browser is not returning an error, it just keeps loading. I don't think you have to configure anything else. If so then they left it out of the instructions: https://youtu.be/F83QTND3Yp8

The client gets an ip address from the vpn pool 10.10.0.6. There are no errors in the openvpn log. I don't have any nat rules

KLX wrote

  @debruina Once you make the connection, are you getting the same public IP as your network, if so, you are halfway there, I am thinking you have to forward a port on the 605 to access your web server. Are your network shares running on equipment with an ip addresses, if so you might have to also open a port to access those shares. meaning, to access your web server via an IP address you would have to include the IP:port number. 

  @KLX 

No it get an ip address from the vpn pool: 10.10.0.6

I am not trying to access a network share. Its just a website running on the local network. Nothing fancy

  @debruina 

Is there any Access Control settings on your router?

Somnus wrote

  @debruina 

Is there any Access Control settings on your router?

No, there are no acls. Its all pretty straightforward. It's just one interface, no vlans or anything. The only thing i can think of is that in release 5.6.4 a few things have changed for openvpn and it also needs a firmware update for the gateway that had not yet been released. But i guess openVPN worked before this 5.6.4 release

Wireshark shows lots en lots of [TCP Dup ACK] errors.

I switched the openVPN protocol from UDP to TCP and it works right away. No idea if it is caused by the router or some UDP traffic is blocked by the cellphone provider.

I have a problem with OpenVPN after upgrading the Controller from 5.5.7 to 5.6.4, It stopped working and will not connect at all tried deleting and recreating the VPN but it didn't help. I switched to L2TP for now that is working.