NodeBB website integration

General Discussion

Suggested Topics


  • 0 Votes
    1 Posts
    23 Views

    I use nginx proxy manager to proxy the ip and port of the Docker container, which is started from GitHub's Docker-Compose, but it doesn't seem to work.

    e7504928-fb47-47d0-a9c3-ea03ce9fade8-image.png
    da6af99b-0e0a-4c7c-b632-34018168a69b-image.png
    b6ffee8d-0840-4380-b395-9ed6f0d27c0f-image.png
    c3f487eb-9485-4679-92f1-29a3778cf5c1-image.png

  • 0 Votes
    2 Posts
    51 Views

    It looks like you are making GET calls to those endpoints. They do not accept the GET method.

    Check the method in the documentation, likely it's one of POST or PUT.

  • 0 Votes
    4 Posts
    2k Views

    @julian said:

    The idea is they're compatible, although I think at the moment, it only works with 0.4.x of Ghost...

    Thanks for your reply. I will try with ghost 0.4.x then.
    Thank you very much.

    UPDATE: I've just tested the plugin with version 0.4.2 of Ghost and all ran smoothly. The problem for me was the "Same Origin Policy" testing the plugin in my local instances of Ghost and Nodebb. I will now re-try the installation with the latest version of Ghost and let you now if i find any problem. Thanks again. 😃

    UPDATE2: I've tested the plugin with version 0.5.8 of Ghost. I get an error related to the ghost API. Even logged in the api responds with 401 unauthorized. I think that is the step involved of publishing the post from ghost to nodebb (while fetching the blog entry content). Think this issue is already known by @psychobunny . Fun fact is that i can post comments en entries already published on nodebb and all works good.

  • 0 Votes
    16 Posts
    4k Views

    Thanks @a_5mith , @julian

    I will just try and take backup and upgrade when it is ready.

  • 1 Votes
    17 Posts
    5k Views

    @julian It's in a container created by the plugin which also is meant to tie it to the forum container. I think you are right that it can't interpret the address correctly as I just tried a clean install but this time with mongodb and that plugin and had the exact same issue.