thorium220

Members
  • Posts

    3
  • Joined

  • Last visited

thorium220's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Yup, that's set. I've attached censored snips of nextcloud's config, swag's nextcloud proxy config and my port forwards in pfsense (just as a hail mary) I've also checked out some of SpaceInvader1's older videos on configuring LetsEncrypt for external access and, aside from some UI changes that have occurred over 4 years, all else seems the same and correct. Checking again from my laptop on my phone hotspot (i.e. outside my network) I'm now getting a failure to connect, not even the 502 I was getting previously. I've attached a snip from cloudflare in case I've got some bad config there too. each censor is colour coded where I've erased the same data over again. I'm very much learning as I'm going here, and probably running before I can walk.
  2. I've been following the 2021 version of this guide (sorry if it's got its own thread, I failed to find it), and at timestamp 22:40 I get a "this site can't be reached (refused to connect)". I've double-checked my work. I've found out that I needed to add host overrides into PFSense which I've now done. Now if I try to connect from an external address (connected my laptop to my phone's hotspot) I get a 502 gateway error from nginx but no change to the behaviour from internal locations, so it seems as though the passage through my router is correct, but something's not quite right here and honestly I'm not even sure where to start troubleshooting. I feel like there's a lot of moving parts in this tutorial, so please feel free to let me know where the most likely culprit is and I'll start screenshotting.
  3. I have had this same error today, I've attached my diags. I'm also in a similar position to OP being a complete newb; this server's been running for about 5 weeks now. I'm assuming that @trurl's instructions to remediate the issue will work for me as well, but I think the source of my error is different. I can track the approximate time of this error commencing to me completely filling my cache drive during some large transfers, but my ability to interpret the exact cause from the syslog just isn't up to scratch. This is a re-used SSD that used to be a boot drive before I refreshed my main rig. tower-diagnostics-20211105-2007.zip