Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to setup a VPN server on 1&1 VPS.

I was able to install OpenVPN-AS more or less as instructed; separately, I have checked and cat /dev/net/tun/ yields

cat: /dev/net/tun: File descriptor in bad state

So that seems alright per the documentation. I have run ovpn-init several times with the default settings without trouble.

The service starts appropriately; service openvpnas restart yields

Restarting openvpnas                                       [  OK  ]

There are no subsequent complaints in /var/log/messages/. When I use nmap to check if the VPN port is open (943 in this case), it is not; in any event, I cannot connect to the admin control panel via http://myserver:943/admin/.

When I run /usr/local/openvpn_as/scripts/sacli status, I get the most informative output:

ERROR: --sock parameter ('/usr/local/openvpn_as/etc/sock/sagent.localroot',
'/usr/local/openvpn_as/etc/sock/sagent') doesn't point to active socket:
sagent/sagent_entry:58, sagent/sacli:792,util/options:79,sagent/sacli:298,

(line breaks added for legibility)

I have Googled this error in about every possible permutation, but I can't seem to find anything. If it matters, the directory referred to (/usr/local/openvpn_as/etc/sock/) is empty, so it's not surprising that the nonexistent parameter doesn't point to an active socket. How can this be fixed?

Many thanks.

share|improve this question
When the VPN is running, you can see anything into that directory? – fboaventura Feb 12 '13 at 10:18

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.