Still if assets are not loading then probably the paths Caddy is serving from are incorrect. So view the logs and web inspector to see which files are failing and then make sure those are available. If they report 404s it’s probably just an issue with the paths, if it’s 403 or something it’s probably because the server is matching against some kind of restriction, etc.
I deleted the tt-rss folder from /var/www/
and trying to clone from git and i get error repository not found (unfortunately i not able to post links here)
after cloned, then moved my backed up config.php to the tt-rss folder, i ran tt-rss from web ui and it told me to chmod five different folders within, i did that. now back to login screen and the login screen itself not have css applied.
what am I missing?
Also checked caddy log and i don’t see any error yet.
i can suggest checking in browser F12 console (network tab) for errors related to CSS files, then check your http server logs for errors (also related to CSS files) and go from there.
do all that in a clean browser profile, without addons, or an incognito window to exclude addons like adblock blocking parts of tt-rss by mistake.
i have no idea what “Caddy” even is so i can’t really help you with it specifically.
also, try doing view source on tt-rss index page and post <link> elements related to CSS, i.e.
It’s not loading CSS, how can there by nothing in the inspector? In most browser’s the inspector has a Network tab. Click that, then refresh the page and look for errors in the requests.