• Home
  • Categories
  • Recent
  • Popular
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Default
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Quartz
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Slate
  • Solar
  • Superhero
  • Vapor
Collapse

Community

Peter-Zoltan KeresztesP

Peter-Zoltan Keresztes

@Peter-Zoltan Keresztes
About
Posts
191
Topics
24
Groups
0
Followers
1
Following
1

Posts

Recent Best Controversial

    Is it bad for performance to have a NGINX reverse proxy ?
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    I am running nodebb on nginx with letsencrypt. I don't see any difference from running it directly.


  • Using nodebb with haproxy as a frontend
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Hello,

    I am trying to setup nodebb with haproxy instead of nginx as frontend. Everything seam to be working however I am getting lots of 403 on /socket.io/ requests.

    frontend http-in
    mode http
    bind 0.0.0.0:80
    redirect scheme https code 301 if !{ ssl_fc }
    
    frontend https-in
    bind 0.0.0.0:443 ssl crt /etc/letsencrypt/live/test/test.pem
    http-response set-header strict-transport-security "max-age=31536000; includeSubDomains"
    http-response set-header Content-Security-Policy "default-src 'self' wss: https: *.startech-rd.tk/*; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://code.jquery.com; style-src 'self' 'unsafe-inline' https:; img-src 'self' https://casper.ghost.org/ https://www.gravatar.com/ data:; font-src 'self' https:"
    http-response set-header X-XSS-Protection "1; mode=block"
    http-response set-header X-Content-Type-Options "nosniff"
    http-response set-header Referrer-Policy "no-referrer"
    reqadd X-Forwarded-Proto:\ https
    acl is_websocket hdr(Upgrade) -i WebSocket
    acl is_websocket path_sub -i /socket.io/
    use_backend bk_ws if is_websocket
    acl acl_comments path_beg -i /comments
    use_backend comments if acl_comments
    
    backend comments
    mode         http
    balance      leastconn
    timeout      connect 1s
    timeout      server  600s
    timeout      queue   600s
    option redispatch
    retries 3
    acl is_woff capture.req.uri -m sub .woff
    acl is_ttf capture.req.uri -m sub .ttf
    acl is_eot capture.req.uri -m sub .eot
    http-response set-header Cache-Control public if is_eot or is_woff or is_ttf
    http-response set-header Expires -1 if is_eot or is_woff or is_ttf
    http-response set-header Pragma cache if is_eot or is_woff or is_ttf
    cookie nodebb insert indirect nocache secure
    
    server node1 10.160.125.81:4567 cookie nodebb_node1 check inter 1000 fastinter 500 rise 2 fall 1
    server node2 10.160.125.82:4567 cookie nodebb_node2 check inter 1000 fastinter 500 rise 2 fall 1
    
    backend bk_ws
    option redispatch
    balance roundrobin
    option forwardfor
    option httpclose
    server node1 10.160.125.81:4567 maxconn 30000 weight 10 cookie ws_node1 check
    server node2 10.160.125.82:4567 maxconn 30000 weight 10 cookie ws_node2 check```
    

    I have tried to connect directly without haproxy and the websockets are connecting correctly. However I've seen that using the haproxy the websocket protocol changed from wss to https.

    Any suggestions on how to fix this?


  • How to install NodeBB on Debian 8 (jessie)?
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @Hillcow Sites-available and sites-enabed does only exist if you install the nginx from the OS repository if you install from any other repository you will only have conf.d which is a good place to put your configuration with the small change that the files in there need to end with .conf extensions.


  • install on wp site
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @absurdsmash

    First of all change the server_name for to forum.mydomain.com and restart the nginx. Second of all please show the configuration of default and 22222 so that we can find out which is the proper config for mydomain.com.


  • install on wp site
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @absurdsmash By virtual host I mean your nginx configuration for a different domain/subdomain.

    Basically you have an A record for

    301 Moved Permanently

    favicon

    (mydomain.com)

    but you missing the A record for forum.mydomain.com. Once that is done and is resolving correctly you will need to add another config file to /etc/nginx/conf.d or /etc/nginx/sites-enabled for forum.mydomain.com


  • install on wp site
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @absurdsmash said in :

    gital ocean networking s

    First of all you don't have any records for forum.mydomain.com that's exactly the DNS error you see in your browser. For using this setting you will have to create a complete new virtualhost configuration.

    Only adding as mydomain.com/forum you would need to add the configuration to the mydomain.com virtualhost settings.


  • Status v1.1.1
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @teh_g It works every time in here. Finally no issues.


  • Status v1.1.1
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Does not seam to be lagging for me. If I write codes inside the composer the preview it's slower a little but but I guess cause it needs to parse the code and apply different colors depending on what's inside it. But hey I can wait 2ms until it shows up. It's not like it's lagging tens of secconds or even minutes.


  • Status v1.1.1
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    upgraded,

    Logs shows some minifier file not found but blog works OK so far.

     [minifier] file not found, node_modules/nodebb-plugin-composer-default/node_modules/screenfull/dist/screenfull.js
    

    here is the error I've told about.


  • install on wp site
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Can you try starting it in developer mode with:

     ./nodebb dev
    

    and give us the output of the startup.


  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    said in :

    <span id="nodebb-comments-count"></span> Comments

    also I have put into the partials/loop.hbs

         <span id="nodebb-comments-count"></span> Comments
    

    to show the number of comments in each posts but this is all I can see:

    http://prntscr.com/c39w38


  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Bingo, that was it. Thanks a lot for your help


  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Did the change but no luck at all.

    301 Moved Permanently

    favicon

    (prntscr.com)

    Here the comments should show up.


  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @psychobunny said in :

    I have no idea how this would have worked for you prior to the upgrade, unless you modified this line while trying to debug your code. This ought to fix it though.

    Actually this line was

    nbb.url = 'https://z0z0.me/comments';
    

  • install on wp site
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Install Nodejs, mongodb/redis and everything else what's needed by nodebb to run. Setup the nodebb and then configure the nginx to work as a subdomain. Not really a brainsurgery.


  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Here is my posts.hbs related to this plugin on the ghost side:

    74             <a id="nodebb/comments"></a>
    75             <script type="text/javascript">
    76             var nbb = {};
    77             nbb.url = 'z0z0.me/comments'; // EDIT THIS
    78 
    79             (function() {
    80             nbb.articleID = '{{../post.id}}'; nbb.title = '{{../post.title}}';
    81             nbb.tags = [{{#../post.tags}}"{{name}}",{{/../post.tags}}];
    82             nbb.script = document.createElement('script'); nbb.script.type = 'text/javascript'; nbb.script.async = true;
    83             nbb.script.src = nbb.url + '/plugins/nodebb-plugin-blog-comments/lib/ghost.js';
    84             (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(nbb.script);
    85             })();
    86             </script>
    87             <script id="nbb-markdown" type="text/markdown">{{{../post.markdown}}}</script>
    88             <noscript>Please enable JavaScript to view comments</noscript>
    

    and here is the nginx config related to this:

    location ^~ /comments  {
    	proxy_set_header X-Real_IP $remote_addr;
    	proxy_set_header X-Forwarded-Proto $scheme;
    	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    	proxy_set_header Host $http_host;
    	proxy_set_header X-Nginx_Proxy true;
    	proxy_pass http://comments_upstream;
    	proxy_redirect off;
    	proxy_http_version 1.1;
    	proxy_set_header Upgrade $http_upgrade;
    	proxy_set_header Connection "upgrade";
    }
    

  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @psychobunny said in :

    Any errors in the browser console?

    No errors only this warning:

    6/8 19:11 [19025] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
    
    • nodebb-plugin-blog-comments

  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    Can I have any help on making this working again? I have done everything what it is in the documentation and it's not working since I have upgraded to v1.1.0 and I had to add proxy_set_header X-Forwarded-Proto $scheme; to the nginx. `


  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @psychobunny said in :

    anything related to publishing and commenting have changed since the

    Any suggestion on how to debug it to eventually make it show up on the ghost posts?


  • [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
  • Peter-Zoltan KeresztesP Peter-Zoltan Keresztes

    @psychobunny Interesting. Any idea why suddenly after updating the nodebb all the comments from my ghost ware gone? I mean on the Ghost site cause I can still see them in the nodebb.

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
  • Login

  • Don't have an account? Register

  • Login or register to search.