Dhagon

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by Dhagon

  1. Hi, I also just got a "Call Traces" error as well, it seems to have happened when I accessed the webui and manually updated my dockers after seeing they failed auto-update for some reason. I recently setup Pihole, and forgot to change the server dns settings, so my guess is that once it tried to auto-update, it shut down Pihole and couldn't use it as dns and the update failed. The server seems to work as usual as far as I can tell, but I don't know what the message means exactly, hopefully someone can clear it up for me. I've attached a txt with the call traces isolated along with the diagnostics.zip, if that makes it easier on you. call traces.txt server-diagnostics-20180328-1153.zip
  2. I've thought about that, but I don't understand how that only affects traffic coming from my PC? If it was redirecting to somewhere wrong using port 80, wouldn't that happen on my phone, too?
  3. Yeah, that was my first conclusion as well, that's why I was hestitant on posting here in the first place, and then I discovered the HTTPVAL problem like everyone else. I just can't figure out what it could be. I've tried different browsers; edge, firefox, chrome; same result across all of them, cleared cookies and browser cache, no difference.. The more I try to fix it the more I think I've over complicated this and missed something really simple. At least you got confused too.
  4. Yeah, me too, but I actually CAN connect from my LAN connection, here's what I've tested; domain.com/service - works for external user and my phone connected to LAN, but NOT on my PC (timeout error). public IP:port (had the port configured before I switched to letsencrypt) - works for external user and my phone connected to LAN, but NOT on my PC (timeout error). local IP:port - works on my PC, but not for my phone. This really bugs me, since I had no problem accessing either on my PC before this happened, and now after getting them working again, my PC is blocked somehow. We've already confirmed my docker and ports have been properly setup, and since nextcloud works via domain.com/service for everyone but my PC, we can rule out duckdns config as well (correct me if I'm wrong), and if the issue was NAT at my router, then my phone would experience the same problem, yes? My phone and PC being on the same network, only difference is my phone using wifi and my pc being cabled, shouldn't make a difference.. I just don't understand, I haven't changed anything other than applying the fix needed for letsencrypt?
  5. Yeah, I read about unraid 6.4 using port 443, but I changed that to another port right away to avoid conflicts. I still don't get how my own PC is the only client unable to connect when I had no issues prior to this, though.. I don't think upgrading to 6.4 had any impact on me not being able to connect, as it was happening before that.. Haven't made any changes to my router either, so I don't think NAT is the issue either.. I just tested again, as I was using local ip:port before, but hadn't tried public ip:port, and seems I can't connect using public ip:port either, but using the same method works for other devices. All attempts from my PC except local ip:port results in timeout errors.. I can ping both the url and public ip as well, so it seems like it just doesn't redirect from my IP or my PC is blocked somehow? if that even makes sense..
  6. Well it had been working before this update.. Now nextcloud works with the fix.. And after updating Unraid to 6.4, ombi started working again for some reason.. Now my problem is that I can't connect to either of them via reverse proxy from my own PC using the same url, only using IP:port works.. Url works for my phone and my friends PC externally.. It really sounds unrelated, but it only started happening once this letsencrypt change of port thing came along..
  7. Here's the docker run cmd and the forwarded ports, not sure if the attached LE log is the one you wanted, let me know if you need more. I haven't changed anything in the docker settings or my router, other than applying the "HTTPVAL = true" fix.. I'd guess I was having the same issue as several other people, with ISP blocking port 80, but since nextcloud works with the fix, just ombi that stopped working, it doesn't really make sense..
  8. All right, sorry, I just didn't want to flood you various logs and screenshots right away, as I'm not entirely sure that it's caused by this container, apart from ombi being inaccessible.. What additional information would you need to assist me? I don't really know which logs would be useful..
  9. After applying the HTTPVAL fix, Ombi became completely inaccessible. I've mapped the ports (internal port 81 -> external 80, 443->443) and forwarded them on my router, and this setup had been working for almost a year before this.. Also, for some reason, I can't access nextcloud on my PC (timeout), but it works on my phone using the same URL.. Also had some friends test this with no errors on their phones and/or PCs..
  10. Hey guys, I've got a problem that I've somewhat narrowed down to being either reverse-proxy related and/or caused by my PC, but I got stuck, so now I'm hoping some of you may know what's wrong. I'm sure that there's some really simple solution that I'm just not seeing, but here goes; I have a basic Unraid server running lets-encrypt, duckdns and a few others, with Nextcloud and Ombi setup on reverse-proxy. Everything has been working flawlessly so far, for almost a year, then suddenly a few days ago, I could no longer connect to Nextcloud or Ombi. I'm able to ping the server by IP and name "myserver.duckdns.org", but I get timeouts when trying to access Nextcloud both via the desktop app and web interface by url myserver.duckdns.org/nextcloud. At first I started looking through settings on the server and router, but then I got a friend of mine to test on his end, and he had no issues accessing either of them. Also found out that I had no issues on my phone connected to the home WiFi.. So my PC is basically the only device unable to connect? I hadn't made any changes on my PC or the server, so this is really confusing. Also, on top of that, I just had the same problem occur as many of you got after the update, but after applying the fix, Ombi became completely inaccessible, this time also for everyone else. Anyone know what could be wrong? Let me know if you need any logs or screenshots.