@PitaJ Yes, I am using http://localhost:4567 to access the forum. It seems I got it wrong how URL variable works. And as I am using the default port everything work it when I changed my config and mislead me to believe that was something wrong with the plugin.
Thank you!
NodeBB could not reach the package manager
-
I keep getting this error when I try to install plugins.
-
Same Error here... did update etc. no change...
Any solution to this?
Or a hint where to look into?
ThX
-
Peculiar. NodeBB installs are set up to install the latest version if the package manager cannot be reached, although of course, that is not always the best course of action
The package manager looks up to me... is it still throwing that error for you? Check the browser inspector "Network" tab. What URL is NodeBB trying to ping?
Edit: https://packages.nodebb.org/api/v1/suggest?package=nodebb-plugin-imgur&version=0.6.1
-
Not shure if I'm doing it correct:
Tried to intall a Plugin, getting the above error message... here a screenshot of Browser Network:
Is that what youve asked for? -
I'm getting this in the console.log
XMLHttpRequest cannot load https://packages.nodebb.org/api/v1/suggest?package=nodebb-plugin-emailer-ssl-smtp&version=0.7.0. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://........com' is therefore not allowed access.
-
@thewheat said:
I'm getting this in the console.log
XMLHttpRequest cannot load https://packages.nodebb.org/api/v1/suggest?package=nodebb-plugin-emailer-ssl-smtp&version=0.7.0. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://........com' is therefore not allowed access.I'm getting this error too, yerterday and today.
-
I also got this error.
-
Most likely related to the removal of https://github.com/NodeBB/nodebb-package-manager/commit/bb079befc7af0d74fa12a11b855a4bb9057bffae#diff-2b137e40025e00eb45b66941ad8d4ddfL148
-
@julian said:
@xbenjii that should have no effect on the package suggestions system... navigating to the url provided seems to work fine as well...
But they're accessing it cross-domain aren't they? Is this not a CORS issue?
Assuming this is the code issuing the error.
In https://github.com/NodeBB/nodebb-package-manager/commit/bb079befc7af0d74fa12a11b855a4bb9057bffae you removed all the middleware, including the CORS header.
-
As of today, using NodeBB v0.7.2, the bug is still present, and the circumstances seem to match the ones described by other users here.
-
Can confirm this is the case for my self also, Unable to update persona theme.
-
Now it appears to be solved
