Jump to content
Not connected, Your IP: 34.204.187.106

Search the Community

Showing results for tags 'Certificate'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Frequently asked questions
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP
    • Mirrors

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 3 results

  1. I just installed OpenVPN for Android on my phone today. After some phone buggy-ness and fiddling, I got it all working. Cool. But I noticed that when connecting to AirVPN, I was never asked for my login+pw. Hmmm... Ok, I now figure the .ovpn files I generated and imported have some keys/certificates embedded that authenticate me personally as the user who needs to login/connect to AirVPN. If that's true, and if my phone is stolen, how can I invalidate those credentials of mine so the thief can't login to AirVPN as me? Will a simple password change on the AirVPN website do the trick? (Thanks, everyone.)
  2. I cannot use the VPN, new installation ! 2017.04.14 15:12:01 - Connecting to Agena (Canada, Toronto, Ontario) .......(all ok until)........ . 2017.04.14 15:12:07 - Flushing DNS I 2017.04.14 15:12:10 - Checking route E 2017.04.14 15:12:11 - curl: (60) SSL certificate problem: unable to get local issuer certificate E 2017.04.14 15:12:11 - More details here: http://curl.haxx.se/docs/sslcerts.html E 2017.04.14 15:12:11 - curl performs SSL certificate verification by default, using a "bundle" E 2017.04.14 15:12:11 - of Certificate Authority (CA) public keys (CA certs). If the default E 2017.04.14 15:12:11 - bundle file isn't adequate, you can specify an alternate file E 2017.04.14 15:12:11 - using the --cacert option. E 2017.04.14 15:12:11 - If this HTTPS server uses a certificate signed by a CA represented in E 2017.04.14 15:12:11 - the bundle, the certificate verification probably failed due to a E 2017.04.14 15:12:11 - problem with the certificate (it might be expired, or the name might E 2017.04.14 15:12:11 - not match the domain name in the URL). E 2017.04.14 15:12:11 - If you'd like to turn off curl's verification of the certificate, use E 2017.04.14 15:12:11 - the -k (or --insecure) option. . 2017.04.14 15:12:11 - Checking route (2° try) E 2017.04.14 15:12:12 - curl: (60) SSL certificate problem: unable to get local issuer certificate E 2017.04.14 15:12:12 - More details here: http://curl.haxx.se/docs/sslcerts.html E 2017.04.14 15:12:12 - curl performs SSL certificate verification by default, using a "bundle" E 2017.04.14 15:12:12 - of Certificate Authority (CA) public keys (CA certs). If the default E 2017.04.14 15:12:12 - bundle file isn't adequate, you can specify an alternate file E 2017.04.14 15:12:12 - using the --cacert option. E 2017.04.14 15:12:12 - If this HTTPS server uses a certificate signed by a CA represented in E 2017.04.14 15:12:12 - the bundle, the certificate verification probably failed due to a E 2017.04.14 15:12:12 - problem with the certificate (it might be expired, or the name might E 2017.04.14 15:12:12 - not match the domain name in the URL). E 2017.04.14 15:12:12 - If you'd like to turn off curl's verification of the certificate, use E 2017.04.14 15:12:12 - the -k (or --insecure) option. . 2017.04.14 15:12:12 - Checking route (3° try) E 2017.04.14 15:12:15 - curl: (60) SSL certificate problem: unable to get local issuer certificate E 2017.04.14 15:12:15 - More details here: http://curl.haxx.se/docs/sslcerts.html E 2017.04.14 15:12:15 - curl performs SSL certificate verification by default, using a "bundle" E 2017.04.14 15:12:15 - of Certificate Authority (CA) public keys (CA certs). If the default E 2017.04.14 15:12:15 - bundle file isn't adequate, you can specify an alternate file E 2017.04.14 15:12:15 - using the --cacert option. E 2017.04.14 15:12:15 - If this HTTPS server uses a certificate signed by a CA represented in E 2017.04.14 15:12:15 - the bundle, the certificate verification probably failed due to a E 2017.04.14 15:12:15 - problem with the certificate (it might be expired, or the name might E 2017.04.14 15:12:15 - not match the domain name in the URL). E 2017.04.14 15:12:15 - If you'd like to turn off curl's verification of the certificate, use E 2017.04.14 15:12:15 - the -k (or --insecure) option. E 2017.04.14 15:12:15 - Routing checking failed. . 2017.04.14 15:12:15 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100 ! 2017.04.14 15:12:15 - Disconnecting
  3. Hi All, I have a Debian Apache Server running on a machine under my home network. I have a opnevpn client and a AirVPN host running especially for the server. But all the incoming connections over ports 80 (http) and 443 (https) are not accessible now from the publicly assigned IP address by AirVPN. I have tried port forwarding some arbitary port >2048 to internal port 443 using Remote Port Forwarding and it works fine. But now I wanted to have a SSL certificate provided by https://letsencrypt.org/ but their client only checks and updates the certificates over SSL port 443 and that is true for all the SSL certificate providers. Is there any I can get the requests go through the VPN?
×
×
  • Create New...