@robi Yes, sorry, I just followed the tutorial that was previously posted by @scooke
https://cloak.ist/blog/how-to-put-a-ghost-blog-at-a-subdirectory-using-cloudflare-workers/
Just wanted to say I've also hit just this issue. Cleaning up the nginx app config files did the trick but I wonder if this can be avoided in the future? Or may be it has already be addressed and I'm only hitting it because of some legacy stuff from previous Cloudron version? (this instance is currently running 7.5.0 but hasn't had a fresh install in a long while).
@ashkaptsov So, AppGyver's browser UI is going to make requests from the browser to n8n and baserow ? Can you tell us a bit more as to why would it want to do that? In general, adding CORS headers without knowing the app knowing about is a security hole.
@mastadamus thanks so much for investigating. I have removed it for next release (7.1) - https://git.cloudron.io/cloudron/box/-/commit/6492c9b71f80120413ff4ae7eefa2f03dc96ea0f
I am currently debugging that instance, but just for others to read up, using nginx -s reload as root usually reveals the syntax errors in config files right away, like it was in this instance as well.
nginx configs became corrupt. Once we got nginx up, it uninstalled. I am putting notes on why nginx configs were corrupt at https://forum.cloudron.io/topic/5457/site-is-not-reachable
@nebulon there was no error reported by cloudron. The issue was that if I tried to curl, there was nothing returned back (I don't remember the exact reply -- sorry for that). Basically it was like nginx was not routing properly, as if nothing was running at the subdomain.
I patch the my.domainname.fr.conf with the missing part (taken from my other Cloudron server).
I then uninstalled and re-installed jingo, and everything seems to work fine now.
Sorry @marcusquinn dident see that you was using ghost for your blog.
in that case, SP_mod will be really a bad choose because front-end and back-end are separate similar on how angular/react works.
I really advice you do optimize your image manually for now, and w8 ghost will release some improvement on that.
@girish I think all these % numbers are a bit misleading and opinionated - but as you rightly detail it's a case of looking at the appropriateness of each item and reasonability.
It's impossible to know or remember everything but still a nice too for a quick review to see if there's any easy wins, and I suppose the scoring mechanism could be handy marketing for some once a certain level is considered reasonably hardened.
Changed As it is the default configuration for Roundcube it is working like intended and we could leave it like this? I don't think its a rare use case but maybe it could be added to the documentation (which I always found very helpful).
