-
|
Hello! What I have done so far:
The container is then successfully created and I can access the web interface. Under Logs I can also see the connection to my server. But on the status page it says "Fix your configuration" and the OpenVPN version is not displayed. I hope you can help. |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 11 replies
-
You can't use localhost 2080 here. You have two options: the first is to use 0.0.0.0 2080 in server.conf, and the IP address of your OpenVPN server followed by :2080 in Configuration-Settings-Management Interface Address. (for example: 192.168.1.100:2080) The other option, which is better as it doesn't expose the management interface to your LAN, is to use 172.17.0.1 2080 in server.conf and 172.17.0.1:2080 in Settings. This is the IP of the default Docker Gateway, so all interaction with the Management Interface happens through this limited gateway. These values are suggested when you look at the help blocks under each data item in Configuration - OpenVPN Settings and Configuration - Settings. Be sure to make the change to your server.conf file first (best done by duplicating the initial server.conf directives in the WebUI) and reboot or restart the OpenVPN service. Once you've done this once the values will be stored in the database. Also, just to confirm, you are using OpenVPN 2.5.x or higher right? |
Beta Was this translation helpful? Give feedback.
-
|
Here's what I'm talking about from Configuration - Settings:
|
Beta Was this translation helpful? Give feedback.
-
|
And from Configuration - OpenVPN Config:
Be aware all of the values need to be correct the first time you create a server.conf using the WebUI. Have the PiVPN created server.conf file open in another window so you can copy and paste as needed. After that first time through, your OpenVPN-Admin-Plus database values will match the actual server.conf file. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, now it works. I have quite a few other questions. Should I ask them in this thread or open new ones? |
Beta Was this translation helpful? Give feedback.
-
|
Here is fine. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Status page refresh is fixed at 60 seconds
Overall client data in/out is in MB and individual client data in KB. We tried a few combinations before settling on this one.
That's the address that will be used when you generate client .ovpn files. Your static public IP, or DDNS address if your IP is Dynamic.
Part of the initial setup is to enter your server.conf data once. Don't skip this or you'll have a variety of issues.
No. But I think you'll find that many of the fields already have the correct data. Being able to change the server.conf file through the WebUI is part of what OpenVPN Admin Plus is all about.
Not sure I totally understand this question. The status page shows connected clients. The certificates page is for managing client credentials -- i.e. creating .ovpn or .conf files for your clients to use to connect. Certificates can be revoked and then removed if you want to discontinue someone's access. Does that answer it? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help. I‘ll post my config later. First I Continue with my questions:
So I should define this parameter also if I neither want to change anything in the config nor create new users??
No, that does not answer my question. I was wondering why a user who is connected according to the Status page is not listed on the Certificates page. One more question: |
Beta Was this translation helpful? Give feedback.
-
If you don't do the initial configuration for OpenVPN config, then that would be the result -- no accurate certificate creation for new users, no ability to change single elements of the server.conf, and I don't believe you'd get persistent log data. This would be an unusual way to use OpenVPN Admin Plus, and I wouldn't recommend it -- though the status page should still be accurate (untested for use in this way though).
Any users created through this WebUI or PiVPN should show up in the list of valid certificates. If they don't there's something amiss with your installation. How was this user created?
These parameters slightly improve the EasyRSA cryptography, through additional "randomization". They're detailed here in the README:
|
Beta Was this translation helpful? Give feedback.
-
|
The user was created with pivpn. In fact, I want to use the tool only for monitoring. I want to know who is online, what bandwidth is/was used. And preferably a history. |
Beta Was this translation helpful? Give feedback.
-
|
Making a backup of your original server.conf file is always a good idea, especially if you're not super familiar with OpenVPN's directives. Don't name it anything with .conf though -- I usually use server.pivpn for my backup. If you're new to Linux, having Cockpit installed with the Navigator plugin is really handy for "system" tasks. I used the command line for so many decades that one of my missions in life is to use it as little as possible from here forward. ;-) |
Beta Was this translation helpful? Give feedback.
-
|
If it'd help, send me a screenshot of your completed Server - Config (blur the port if you know how -- but even that's not really critical), and I'll tell you if I see any potential issues. Be sure to expand the Extra Server and Client Options so I can see everything in those fields. |
Beta Was this translation helpful? Give feedback.
-
The Certificates page is intended for issuing, revoking and deleting certificates from the database, not for monitoring! This page also allows you to download ready-made configurations (.zip or .ovpn) for your OpenVPN Client. Important! Using the certificate removal function from the database, keep in mind that it is deleted from the file index.txt which is necessary for forming a revoke list. If you delete a certificate from the database, it does not get into the new revocation list. |
Beta Was this translation helpful? Give feedback.
-
|
I am using openvpn-admin-plus now a few days. I am happy with the fact that I can watch the current users and their traffic on the status page. However, I am surprised that even after restarting the whole computer, my log continues to show data from 06 February 2023, although today is 14 February. |
Beta Was this translation helpful? Give feedback.
-
|
The log will get setup correctly once you run through entering data into Configuration - OpenVPN Config the first time. The OpenVPN Admin Plus database will be populated, and a server.conf file with your directives, plus a few needed for the full WebUI functionality will be generated. Have your current server.conf open in another window as you're entering the data. Many fields will already be correct. Save & Apply followed by an OpenVPN restart or system reboot and you'll be good to go. Saving a copy of your current server.conf as server.pivpn first is always a good idea. |
Beta Was this translation helpful? Give feedback.
-
|
I hope I have understood you correctly? I have not used openvpn config and do not want to use it because I do not want to change my server.conf. This has the consequence that log does not work? |
Beta Was this translation helpful? Give feedback.
-
|
You would have had to modify server.conf to even get this far, by adding a "management" directive. This is similar, and will be done for you through the WebUI. Do you prefer to modify server.conf manually? |
Beta Was this translation helpful? Give feedback.
-
|
There are a few log file directives that need to be added or modified to give Docker access to the log. This can also be done by directly editing server.conf, as you did to get the management directive in there. Doing it via the WebUI is simply intended to make it easier, and would have taken care of all this for you. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I already modified the server.conf manually. Here is my server.conf: And here are the configuration pages of openvpn-admin-plus:
|
Beta Was this translation helpful? Give feedback.
-
|
The section in your server.conf file that would be updated is: # status /var/log/openvpn-status.log 20
# status-version 3
# syslog
log /etc/openvpn/openvpn.log
verb 3
mute 10This can, of course, be done manually too. :-) Restart OpenVPN or reboot after updating. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much. Now the log works again. I didnt comment out the status command, because I'm playing around with grafana. Now that you see my settings, do you have any idea why a connected user is not listed under Certificates? |
Beta Was this translation helpful? Give feedback.
-
|
Nothing is jumping out at me. Could you post the output of "sudo tree" (you'll probably need to install tree first) from the /etc/openvpn directory, and the contents of /etc/openvpn/easy-rsa/pki/index.txt? |
Beta Was this translation helpful? Give feedback.
@2003flo
You can't use localhost 2080 here.
You have two options: the first is to use 0.0.0.0 2080 in server.conf, and the IP address of your OpenVPN server followed by :2080 in Configuration-Settings-Management Interface Address. (for example: 192.168.1.100:2080)
The other option, which is better as it doesn't expose the management interface to your LAN, is to use 172.17.0.1 2080 in server.conf and 172.17.0.1:2080 in Settings. This is the IP of the default Docker Gateway, so all interaction with the Management Interface happens through this limited gateway.
These values are suggested when you look at the help blocks…