Jump to content
Not connected, Your IP:

Search the Community

Showing results for tags 'generator'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


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

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL







XMPP / Jabber




Found 3 results

  1. I am trying to use the API to generate a .conf file for wireguard. This works fine, curl -H "API-KEY:xxxxx" "https://airvpn.org/api/generator/?system=windows&protocols=wireguard_1_udp_1637&servers=america" but when I try to specify servers by country I get an error. Does anyone have it working for countries? As an aside, the API page mentions, "checking API Reference" on the generator page, but I don't see that option there nor am I able to find an API reference elsewhere.
  2. Hello, I'm one of the Mullvad refugees. While I tried it for a few weeks now, using a peer-to-peer protocol without a forwarded port was just too slow and often it was even impossible to establish connections to peers. And although I'm very happy with your service and the general scope of the API, there are some things that are broken or that I'm missing: Setting device names and descriptions via the API. Assigning ports to devices via the API (preferable by ID and name, but most importantly by ID), maybe also claiming ports via the API. In my tests calls to the configuration generator API with "resolve=on" would only work for IPv4 endpoints, not for IPv6 endpoints. It would be great if this also worked for IPv6 addresses. It seems a bit strange to me that adding a device returns a longer ID, while the other parts of the API which use the ID seem to truncate it to 50 characters. Why isn't the truncated ID returned uniformly? It would be nice for my use-case to also have the configuration generator optionally return JSON. The current configurations are to be consumed by wg-quick and while using wg-quick (either to load them or to transform them to wg rules) or parsing them and using them with wg is easy enough, it would just be nice to have the additional option. Maybe with some nice clean key names like "public_key". Example request for the mentioned IP resolution problem: curl -H "Api-Key: <REDACTED>" "https://airvpn.org/api/generator/?protocols=wireguard_1_udp_1637&servers=europe&device=default&resolve=on&iplayer_entry=ipv6" -o AirVPN_Europe_UDP-1637.conf This will properly resolve the hostname to an IP when "iplayer_entry=ipv4" (or the empty default) is set, but just pass the hostname through when "iplayer_entry=ipv6" is specified.
  3. A number of mobile browsers don't save the file correctly when the Generate button is pressed. Based on my experience just now, one popular browser saves a copy of the entire web page to the .ovpn, another just saves blank files. Rather than try to debug all of these I have a suggestion. Offer a checkbox or button on the Generator page that will display the config right there, in a box, such as an edit field, allowing the user to simply select and copy it to their paste buffer. This will get around filesystem quirks and give the user some flexibility in how to save it on their device. What's more if it's an edit field (textarea) and the user knows of changes they need to make or would like to insert a comment, they'd have the handy ability to do it right there in the web page before copying it. Thanks for your consideration.
  • Create New...