mattie112

Members
  • Posts

    271
  • Joined

  • Last visited

  • Days Won

    1

mattie112 last won the day on July 18 2021

mattie112 had the most liked content!

1 Follower

Recent Profile Visitors

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

mattie112's Achievements

Contributor

Contributor (5/14)

37

Reputation

  1. Yeah, I can understand that, however the downside is that you then have an usecase that is not used a lot and that it can be hard to find a good tutorial. What you can do (as you are just experimenting now): first set it to port 80 so letsencrypt can just give you a certificate. And then change it back to an other port. Your certificate will just work but never renew. Might be a bit easier to set up and give you enough time to try it out.
  2. No you should not do this manually (as it changes every time you'll need certificates). So: you should input your google credentials and then NPM (or really certbot in this case) will do an API call to update the TXT record and then letsencrypt can verify that. (also see: https://certbot-dns-google.readthedocs.io/en/stable/) Is there any reason why you want your webserver on non-80/443
  3. What exactly are you trying to do? Your NPM (= proxy server) is listening on 80/443, you can add a host for anything within that. domainA.com -> 1.2.3.4:80 domainB.com -> 1.2.3.4:81 something.domainC.com -> 1.2.3.5:443 If you have an internal 'service' listening on both 80/443 choose one. Usually internally your services are terminated in 80 (as you don't have a ssl cert for them) but 443 should work just fine (as long as the cert is valid)
  4. You should be able to do that through the UI:
  5. I just have a fork of: https://github.com/jlesage/docker-nginx-proxy-manager into https://github.com/Mattie112/docker-nginx-proxy-manager that only changes the ports That project was not updated since 23 Feb. Are you looking for something specific? Perhaps I can get that part.
  6. Externally you only have 1 IP so you can only 'open' 80/443 once. You don't really 'open' a port btw, you 'forward' it to a different IP. So for example: 1.1.1.1 -> your external IP 192.1.1.1 -> unraid 192.1.1.2 -> VM 1.1.1.1:80 -> 192.1.1.1:8080 1.1.1.1:443 -> 192.1.1.1:443 If you have this you can NOT have 1.1.1.1:80 -> 192.1.1.2:8080 But you CAN do 1.1.1.1:81 -> 192.1.2.8080 But why do you want to do that? The whole idea of NPM (or a reverse proxy) is that you have a single entry point. And that within that proxy you can send 'domainA.com' to server A port B and 'domainB.com' to server C port D
  7. I don't use cloudflare myself but: Can you perhaps try the most simple case? For example with https://hub.docker.com/r/hashicorp/http-echo/ and just let it run on 80. Just to first make sure that cloudflare -> server works.
  8. Nextcloud is on a different IP so that should work. Did you set the port mapping correctly? So 80 on your 'host' and 8080 in the NginxProxyManager for example. Can you show a screenshot of your ports? (If you need NPM to listen on 80/443 for IPv6 for example and you don't use IPv6NAT you can use my fork: https://github.com/Mattie112/docker-nginx-proxy-manager / https://hub.docker.com/repository/docker/mattie112/docker-nginx-proxy-manager)
  9. You can switch over by changing this: Let me know how it works
  10. Yeah or just change the repo url (assuming the env vars are the same)
  11. You could try to write your config to the appdata folder of the importer to see if that works? The inporter expects a filename but does not get anything (for whatever reason)
  12. Is this the log of the importer or firefly itself? It seems to give an error at `convertConfigFile` so you might want to doublecheck your config.
  13. (not in my Version: 6.9.2) Docker version: 20.10.5 Docker vDisk location: /mnt/user/system/docker/docker.img Default appdata storage location: /mnt/user/appdata/
  14. Yeah I don't know. Any problems with other docker containers? Perhaps remove your entire docker.img? The commands I posted should work (and do work on my Unraid, Windows desktop and Linux desktop). So there must be something with your setup. You could also try some basic containers like alpine or something.
  15. What device do you use for your Unraid? It works fine here: root@Tower:~# docker pull jlesage/nginx-proxy-manager Using default tag: latest latest: Pulling from jlesage/nginx-proxy-manager Digest: sha256:488bd69104c9b88ae6a9f7ee6cb3413f8ec63da118034919616bb462c84f61ed Status: Image is up to date for jlesage/nginx-proxy-manager:latest docker.io/jlesage/nginx-proxy-manager:latest root@Tower:~# docker run -it jlesage/nginx-proxy-manager bash bash-5.1# I know that trying to run a x64 image for example on ARM does not work. But yeah I don't know....