@julian @PitaJ this is my result after that I have do fir "./nodebb stop" and after "ps aux | grep node" in Centos:
0_1479735622500_Senzanome.png
I do "vagrant up" to start a centos machine.
After adding 1.1.1 I still get a 404 on the "/pushbullet/auth" url on the forum. So unless pushbullet does a POST request (which nodebb picks up) something still seems to be wrong.
Are you sure /pushbullet/auth is a valid express-route?
@hek As far as I know the allowed_origin
value was not there when I originally set up Pushbullet for NodeBB. It's still empty now for this install, and it seems to be working fine. Let me fix up another bug I found and I'll take a look at the /auth
route, thanks!
v1.1.2 is out, although I can't seem to reproduce your bug @hek. Are you trying to access /pushbullet/auth
manually? You should only be sent there by Pushbullet after granting authorization, and the url should look something like this:
http://localhost:4567/pushbullet/auth?code=5zqyqC67eTI8FaYVt4jYzmDiKeogVbJL&state=
@julian in my case i'm landing on approve pushbullet site and when i click approving small wheel starts turning and never stops
@julian i was missing "http://" now working smooth
And now i'm getting notifications from this one too, sweet!
Got it working in our prod-env now. I have no idea why I couldn't get it started in stage.
Anyhow happy!
@julian the settings page is working, but I still don't receive notifications.
I think I have narrowed the problem down.
The enabled check is looking for a numerical value:
parseInt(results.settings[index]['pushbullet:enabled'], 10) === 1
The data from the db contains a string value (I disabled and enabled notifications multiple times to make sure it's always a string):
settings: [ { 'pushbullet:enabled': 'true', 'pushbullet:target': '' } ]
Anyone else having issues with Pushbullet spinning and not accepting after setup?
Hi, is this plugin working?? I am banging my head now
Step 1#
After creating my OAuth client (https://www.pushbullet.com/create-client)
I need help here, which is the client id / secret ?
1 =
2 = ?
Step #2
Next, i clicked on the oauth test url:
Step 3
3: is this url formed correctly?
ps: Do i need to open certain ports on my server?
Ouch, looks like pushbullet revamped their OAuth client creation page... doesan't look that good right now.
In any case, seems #2 is the OAuth ID and #1 is the secret. As for #3, it should return a code, no clue why it doesn't at the moment. Will have to do some testing and see.
Edit: @Silvina can you download 1.1.8 of the plugin and try associating your account again while you are in development mode (start NodeBB via ./nodebb dev
)? The plugin should now output a debug message when you click "associate"
I'm still having the issue with Pushbullet just spinning when trying to accept the asociation.
This is output in the console when running in dev.
info: [plugins/pushbullet] New association, redirecting user to: https://www.pushbullet.com/authorize?client_id=%ClientID%FromACP&redirect_uri=https%253A%252F%252Fdomain.tld%252Fpushbullet%252Fauth&response_type=code
Followed by:
route requested but not found /pushbullet/pushbullet/settings
Edit: Running latest of plugin on 0.5.2