Nanobug

Members
  • Content Count

    230
  • Joined

  • Last visited

Community Reputation

23 Good

About Nanobug

  • Rank
    Member
  • Birthday 03/02/1990

Converted

  • Gender
    Male
  • Location
    Denmark

Recent Profile Visitors

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

  1. I'm so dumb.... My port forwarding was something like this: 80 --> 8080 443 --> 4443 I think I changed the ports last time, I can't remember why. Now it's: 80 --> 2080 443 --> 20443 I've got 10000 - 19999 assigned for game servers so I don't have to update that range all the time. It works now, thanks
  2. DNS challenge? I just Googled it, and I'm not quite sure what it is, or how to use it.
  3. I've got it reinstalled now. But it wont let me request a new SSL certificate, it says "Internal Error". The docker log says /appdata/NginxProxyManager/log/letsencrypt/letsencrypt.txt says to make sure I made the correct A/AAAA DNS record (I used the same as before, before it broke), and I checked it again, just to be sure. It doesn't tell me what the issue is, or I'm missing it. Do you guys know what it is, and how to fix it?
  4. Everything is on 192.168.100.0/24. I'm in the process of moving it back to bridged, so it's on the same IP, just a different port. I used ot have it all at it's own IP. And yes, I could ping the router: bash-5.0# ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1): 56 data bytes 64 bytes from 192.168.100.1: seq=0 ttl=64 time=0.387 ms 64 bytes from 192.168.100.1: seq=1 ttl=64 time=2.297 ms 64 bytes from 192.168.100.1: seq=2 ttl=64 time=0.196 ms 64 bytes from 192.168.100.1: seq=3 ttl=64 time=0.185 ms 64 bytes from 192.168.100.1: seq=4 ttl=64 time=0.408 ms 64 bytes fro
  5. docker exec -it NginxProxyManager bash bash-5.0# ping 192.168.100.50 PING 192.168.100.50 (192.168.100.50): 56 data bytes --- 192.168.100.50 ping statistics --- 57 packets transmitted, 0 packets received, 100% packet loss bash-5.0# nc 192.168.100.50:32400 bash-5.0# ..... From Windows C:\Users\Nanobug>ping 192.168.100.50 Pinging 192.168.100.50 with 32 bytes of data: Reply from 192.168.100.50: bytes=32 time<1ms TTL=63 Reply from 192.168.100.50: bytes=32 time<1ms TTL=63 Reply from 192.168.100.50: bytes=32 time<1ms TTL=63 Reply from 192.16
  6. Hello, I'm getting a "502 Bad Gateway" error. So I tried to remove the proxy host, and the sub domain, and set it up one step at a time. When I add the DNS record, it points me to the congratulations page. When I add it to the proxy hosts, set it up, it just gives me the error. I have the same issue on other subdomains. I did have it working before. Then I change some IP's and ports, and edited it in NPM as well, and it started doing the same. I'm not sure how to proceed from here. I can use the internal IP and port in a browser, so it works. Am I missing something?
  7. I'm using my router instead. 4 GB. It had 8 GB in the beginning, but I lowered it to test it, and it works just as well as 8 GB.
  8. From work and when I'm not at home. I'm using my servers, but there's thing I can't do, or prefer to do in a VM.
  9. It came back today..... nanostorage-diagnostics-20210408-0825.zip
  10. Dang... I didn't know that, and I thought I uninstalled most of them again, since I looked through what could be used. Must have forgotten that one. Uninstalling it right away. Thanks! I'll let you guys know tomorrow if it continues.
  11. I know a brand new server uses around 1.6 GB of RAM. I think the biggest one I have, RAM wise is just below 3 GB, at peak hours. It seems a bit high to use almost 4 GB of RAM most of a 24 hour period.
  12. Still had the problem today when I checked from work. I've attached the diagnostics. I can also see the log is getting filled up. Where does it say from what so I can adjust it? nanostorage-diagnostics-20210406-0826.zip