Pixelfed "running" but won't load. Backups are all the current version.

[scooke]

A little while ago someone poasted about their Peertube instance not federating. I checked mine. Then I checked my Pixelfed and discovered it isn't even working! Here are the logs:

Feb 08 19:10:20 172.18.0.1 - - [08/Feb/2025:12:10:20 +0000] "GET / HTTP/1.1" 200 1834 "-" "Mozilla (CloudronHealth)"
Feb 08 19:10:23 ==> Running schduler
Feb 08 19:10:24 2025-02-08 12:10:23 Running ['artisan' horizon:snapshot] ..... 459.67ms DONE
Feb 08 19:10:24 2025-02-08 12:10:24 Running ['artisan' story:gc] ............. 424.85ms DONE
Feb 08 19:10:24 ⇂ '/usr/bin/php8.3' 'artisan' horizon:snapshot > '/dev/null' 2>&1
Feb 08 19:10:24 ⇂ '/usr/bin/php8.3' 'artisan' story:gc > '/dev/null' 2>&1
Feb 08 19:10:25 2025-02-08 12:10:24 Running ['artisan' app:transform-imports] 407.80ms DONE
Feb 08 19:10:25 ⇂ '/usr/bin/php8.3' 'artisan' app:transform-imports > '/dev/null' 2>&1
Feb 08 19:10:30 172.18.0.1 - - [08/Feb/2025:12:10:30 +0000] "GET / HTTP/1.1" 200 1837 "-" "Mozilla (CloudronHealth)"
Feb 08 19:10:40 172.18.0.1 - - [08/Feb/2025:12:10:40 +0000] "GET / HTTP/1.1" 200 1832 "-" "Mozilla (CloudronHealth)"

Any suggestions?

[joseph]

This seems like those adamant PWA + service worker things . Blow away the browser cache for that domain or try in another browser , just to verify if this is the problem ?

[scooke]

It was DNS. Man. So, trying different browsers helped me. First, the errors had a 200 return, meaning the site wasn't reachable. I should have figured it out then. Then using Incognito mode in Chrome came back with a cryptic message, the gist of which was that the "received data could not be verified". So, it was "working", as the Dashboard said, but not working. The Firefox also said something similar. So, I checked the DNS... and discovered I had changed the A records for @ and * to another IP. That was for a similarly named domain!

I fixed this DNS error, and I'm back in business.