Jump to content
Not connected, Your IP:

Search the Community

Showing results for tags 'nextcloud'.

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. Hello, New user here with a similar problem, big fan of the service so far. It would help me if this could be dummied down a little. Similarly to OP, this setup works for regular http: webserver > airvpn? > airdns > user Goal: I would like to be able to accomplish this with https (webserver > airvpn? > airdns > cloudflare hostname > user) where each phase is encrypted. Problem: I am unable to register a certificate using the records in the background section. I think I misunderstood what you meant Background: My webserver (cosmos server) expects a hostname and allows you to use letsecrypt with your hostname (and it's subdomains) to encrypt connections with tls. Their documentation has you open a port on your router, then point your domain to your router with these records: A my.domain.here my.ip.address.numbers CNAME * my.domain.here It was working in this configuration. But in an effort to increase security (not a fan of opening up my router to attacks), I'd like to use port-forwarding instead. From the information in this thread I've ended up with these DNS records: CNAME my.domain.here subdomain.airdns.org CNAME * my.domain.here I am requesting a certificate for my.domain.here and it's subdomains (*.my.domain.here). Error: When I try to register a certificate I get this error: cloudflare: failed to find zone airdns.org.: ListZonesContext command failed: Invalid request headers (6003) Googling this error has not turned up many good results, but the error makes sense, I don't own your domain! Questions: First off, is this setup what you meant? Second, is there a way I can change my records to get past this error? Finally, do I need this at all? I can disable https all together but am not clear of the security ramifications (maybe your tls connection with the user is enough).
  2. I have a local Server permanently connected to Airvpn over wireguard. Now I want to access the installed Nextcloud from the internet with SSL Encryption. I use an apache2 webserver. I opened a port and I can access it over http. But I don't know how to configure it over https. https://airdns.org/ has a Let's encrypt certificate, but in my nexcloud.conf I know only how to use a local certificate. So how can I point the webserver to use the certificate from airdns.org?
  3. I have the VPN set up on my router. In the past I have successfully forwarded ports, using iptables, for a torrent client and a subsonic server that's running on a raspberry pi (my subsonic account uses a subdomain on subsonic.org). Now I've installed nextcloud on another raspberry. I can access it locally via the raspberry's ip, but I can't get to it externally. For external access, I'm hoping to use a subdomain on my own website. Here's what I've done: 1. Pointed the A Record of my subdomain (cloud.mysweetsite.com) to my DHCP ip address. 2. Forwarded a port on airvpn.com, using local port 443. 3. In my router (dd-wrt), I set up this iptable: iptables -I FORWARD -i tun1 -p udp -d --dport 15119 -j ACCEPT iptables -I FORWARD -i tun1 -p tcp -d --dport 15119 -j ACCEPT iptables -t nat -I PREROUTING -i tun1 -p tcp --dport 15119 -j DNAT --to-destination iptables -t nat -I PREROUTING -i tun1 -p udp --dport 15119 -j DNAT --to-destination 15119 is the port I forwarded on airvpn. 4. in /etc/apache2/sites-available/nextcloud.conf I'm specifying ServerName cloud.mysweetsite.com What am I missing? What have I done wrong? Perhaps I should ask on the nextcloud forums instead of here! But it just seems like the vpn adds an extra layer...
  • Create New...