Author Topic: [SOLVED] Zentyal cloud not connected: socket bind failed  (Read 2525 times)

Talkless

  • Zen Apprentice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
[SOLVED] Zentyal cloud not connected: socket bind failed
« on: August 29, 2011, 07:52:55 am »
Hello,

Using Zentyal 2.0.22 I noticed in dashboard that:
Quote
Connection status
Not connected. Check VPN logs in /var/log/ebox/openvpn/

And so in /var/log/ebox/openvpn/R_D_SRVS_510c4a851.log log file:
Quote
TCP/UDP: Socket bind failed on local address [AF_INET]192.168.0.4:44120: Cannot assign requested address

The problem is that current Zentyal local address is 192.168.0.2.
*.4 was older IP, I changed it for some reasons. Everything looks normal but the openvpn service.

It looks like even after IP change openvpn uses same old address, how should I fix that?

Thanks.
« Last Edit: September 23, 2011, 12:03:26 pm by Talkless »

sixstone

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1417
  • Karma: +26/-0
    • View Profile
    • Sixstone's blog
Re: Zentyal cloud not connected: socket bind failed
« Reply #1 on: August 29, 2011, 10:08:14 am »
Hi talkless,

Yesterday we release a new package to fix this issue, please upgrade to ebox-remoteservices 2.0.18.

After that, running this command will recover your VPN connection:
Code: [Select]
$ sudo /etc/init.d/ebox remoteservices restart

Let me know if that works for you.

Best regards,
My secret is my silence...

Talkless

  • Zen Apprentice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Zentyal cloud not connected: socket bind failed
« Reply #2 on: August 30, 2011, 07:39:34 am »
Yes, it did helped indeed.

Thank you!

sixstone

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1417
  • Karma: +26/-0
    • View Profile
    • Sixstone's blog
Re: Zentyal cloud not connected: socket bind failed
« Reply #3 on: August 31, 2011, 11:18:51 am »
Great to hear so!
My secret is my silence...