Ghost server - minor issues

Ghost server - minor issues

I changed the title - it was a little misleading

I have temporarily moved my ghost server to the cloud.

Actually its a bit of a bonus, all i have to do is change the CNAME pointer and I swap servers.

Why because I am having serious issues with open-appsec WAF SaaS and the site has been up and down like a yo-yo. So I'll leave it here.

Open-appsec is here, and I haven't yet ruled it out as the problem.

open-appsec | Automatic Open Source WAF & API Security
Open-Source Web Application Firewall & API Security using Machine Learning. WAF alternative for OWASP-Top-10 and Zero Day attacks. Kubernetes, NGINX, Envoy, Kong, Ambassador.

Basically, there is something wrong with the proxy that I cant find. Why the hell it's trying to use SSL before I set it up is beyond me.

Never mind, I have found the problem, just need to find the time to keep testing, all working internally now (ie... LAN) but still testing.

Why the new WAF because my firewall logs are showing that its required. The old solution wasn't cutting it, but that's another story.

I am finally getting back to work, after losing 2 months due to surgery and waiting for it - time has just flown - so I will work this all out in due course.

I will slowly work through all the posts and fix them yet again, and back it all up yet again.

However, deployment via docker is a community driven project and not fully supported and the community forum is extremely busy.

I still think its the proxy in open appsec. I got a good mind to throw it in the shit can and use the full version of NGINX, add the open appsec plugin for Linux in and muck around with some sneaky port diversions.

I so want the appsec Saas webUI functionality.

Sigh.

#enoughsaid