@Braulio-Cesar-Holtz-Ribeiro you need to set the HTTP header for frame options on the site that is displayed inside the iframe.
NodeBB actually has a setting for this in the ACP. You should be able to find it by searching "frame"
(Didn't know where to post there, could be moved to
Okay, so out of no where my site went dead.
I checked to see what was going on and tried using
forever restart app.js ... well that didn't work.
I checked to see if it was forever, so I stopped it using forever and used
./nodebb dev and it hangs here;
xxxx@convoe:/home/xxxx# node app
info: NodeBB v0.3.2 Copyright (C) 2013 DesignCreatePlay Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info: Time: Sun Mar 09 2014 00:09:36 GMT-0500 (EST)
info: Initializing NodeBB v0.3.2
info: * using configuration stored in: /home/xxxx/config.json
info: * using redis store at 127.0.0.1:6379
info: * using themes stored in: /home/xxxx/node_modules
info: Enabling 'trust proxy'
And it stops there. It won't let me stop it, it won't let me close it. It doesn't even run at that point either.
Not sure what to do now.
(It can't be the database because I just setup a new one to check.)
Yep, related issue. Hmm WTF @ 99% CPU ...
It still won't load because the CPU is too high. It works though nonetheless.
System information disabled due to load higher than 1.0
UPDATE: Okay now it's down to 70%. Still a bit high when before it was at a low 12%.
kill -9 the process, update to latest, and run it again. I've just temporarily commented it out.
I hope it doesn't happen every Sunday Possibly only at daylight time switches, though even twice a year is pretty bad.