ok, I think I solved it.
Apparently, after executing commands like
sudo firewall-cmd --zone=public --add-masquerade --permanent
sudo firewall-cmd --zone=public --add-forward-port=port=80:proto=tcp:toport=8000 --permanent
sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8000
somewhat screwed up the firewall rules in the google console. The catch was that I could only acces the website from port 80, by trying to acces it from 8000(node's actual) didn't work. I deleted the rules, and added them again in the platform console (Networking->Firewall rules) and then restarted nodebb and it worked!
@fyhao Great plugin for analytics. I see you're feeding it into https://text-sentiment.p.mashape.com/analyze?
Can you say a bit more about which algorithm they're using? I'm a data scientist and I'd be happy to collaborate a bit on this, but my specialties are Python and R so I'd have to write the machine learning backend in one of those languages for you.
If you don't mind getting your hands dirty you can modify core and change PostTools.parse
I was thinking to extract the topic id from data.url and pass it back to the plugin backend to store, and then limit my plugin to one instance per topic for now. But I think that would be even worst, and when 0.6.0 arrives I would have to fix it anyways.
I am a bit scared to touch the core stuff, but I may give your suggestion a try since it is less hacky, and better long term solution.