Jump to content

aptalca

Community Developer
  • Content Count

    2963
  • Joined

  • Last visited

  • Days Won

    2

aptalca last won the day on March 16

aptalca had the most liked content!

Community Reputation

291 Very Good

5 Followers

About aptalca

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Don't change the port in the proxy confs. They refer to internal container ports. If you're reverse proxying that way, you don't even need to map a port for the container, you can remove them. Or set then to whatever, it doesn't matter.
  2. Glad to hear you figured it out, but it sounds like you didn't follow the troubleshooting guide properly as that test would tell you the IP was not correct for that subdomain
  3. Nginx logs in letsencrypt will show you all the connections. They're in the config folder. Also, if you reverse proxied with all the correct headers, letsencrypt will pass the original ip in there. You may have to tell apache to trust those headers. For nginx, you do it via "real ip" module and settings. Not sure what apache needs
  4. You need to provide more context. Are you reverse proxying the server? And by server do you mean unraid?
  5. Restart the container and it should fix the permissions
  6. The user is abc and its pid is set to 99 (unless you changed it). It should have access to those folders on host
  7. Just a general comment. I'm seeing quite a few people here with the comment "followed spaceinvaderone video, it doesn't work". Perhaps you should ask him for support, maybe there is an issue with the directions there. If you use the default template as is, and follow the directions we provide in the readme (linked in the first post here), it works. I've been using it for years. It only once crapped out on me during an image update, I restored from a backup and it worked just fine since. Also keep in mind that when you update the image, it has to connect to the openvpn-as repo to download the package. If you have networking issues (dns config, mtu issue, or something like pihole blocking it) you'll see in the logs that it is unable to connect to the repo. To ask for support from us, post your docker run, and a full docker log on pastebin or the like and drop links here. Also let us know how you're trying to access it (the address) and what settings you changed in the gui. "I followed X guide and it doesn't work" is not going to get you support from us.
  8. It's explained in the readme, but you really should reverse proxy rather than share certs
  9. Can you post the output of ”ps -ef" from inside the container when that happens?
  10. That line alone is not helpful. All it tells you is that there was an issue with openvpn install. Post a full log if you seek assistance, and post a docker run. Pihole is known to cause such issues
  11. See here https://blog.linuxserver.io/2019/04/25/letsencrypt-nginx-starter-guide/