Can't get pass OpenVPN-AS EULA page #11
Comments
|
That means that something in the environment is missing and Access Server backend cannot function correctly without it. So the web interface may be up but it's unable to function correctly and then it gets stuck at the first screen where it actually really needs to do something. You could open a command prompt to the Docker instance and go through the log file at /var/log/openvpnas.log to see if there are errors there. What I'm kind of suspecting here is that there will be errors related to iptables-restore and such not being able to load because the host doesn't offer that. And Access Server does really need that. If whatever errors are reported in that log file are resolved, the web interface should then function normally. Since log files can contain sensitive data you may instead want to open a support ticket at https://support.openvpn.net/ as you can securely share log file data there, instead of posting it here on github in public. For Synology there is also the alternative to run Access Server as a virtual machine on a Linux OS like Ubuntu 24.04 LTS or such using 'Virtual Machine Manager'. That's a little bit heavier than Docker but has the advantage of being a full OS so it should come with everything necessary to run Access Server, whereas the OS in Synology might be lacking something important that Access Server really needs. |
|
I am running OpenVPN within the Synology Suite "VPN Server". But I wanted to create another OpenVPN instance to be over SSL/TLS in order to avoid DPI in workplace firewalls. below are snippets from the docker log with all sensitive information removed <style> </style>content2024-09-28T08:15:12+0000 [stdout#info] [WEB] OUT: '2024-09-28T08:15:12+0000 [twisted.python.log#info] "172.17.0.1" - - [28/Sep/2024:08:15:12 +0000] "GET /admin/fa-light-300.woff2 HTTP/1.1" 200 157064 "https:///admin/all.min.css" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36"' |
|
I am seeing a loooooot of errors in there so I don't know what's all going wrong there. But the one that really sticks out and is an absolute blocker is the lack of support for iptables; pyovpn.util.error.SimpleError: iptables capabilities error: ('Error verifying iptables capabilities when running following command', ('iptables', '-n', '-L')) This is basically a show-stopper for running OpenVPN Access Server in Docker on your host. I suggest you go the virtual machine path instead and going for Ubuntu 24.04 LTS with Access Server on that on your Synology device. |
|
similar errors we also might see if cap NET_ADMIN is missed in container @mohsh86 could you please share what is your docker (docker-compose) configuration, do you run this docker container under the root and some host specs (like the OS and the kernel) |
|
I also have a similar problem. I am using openSUSE Micro Leap 6.0 [1] running on a Raspberry Pi 3B+. This system uses Podman instead of Docker for running containers. Here is the link to the I am starting rootfull container using this command From inside container I checked: |
|
Hi bckaczynski - I suggest you read my earliest comment on this thread for information on what to do and look for. There are certain basic requirements that Access Server has that are pretty much present on almost all standard Linux systems, but there are exceptions. If certain basic functionality is missing, Access Server runs into an error state and then the web interface cannot proceed. |
Running docker image in Synology NAS. Initial setup went fine.
When navigating to admin page however, I am presented with EULA and an "Agree" button.
no matter how much I click "Agree", the page refresh back to EULA
Chrome debug looks fine
The text was updated successfully, but these errors were encountered: