Has anyone experienced this ?
We are monitoring pm2 services using PM2 monit tool. For notifications we have configured to send the notifications to webhook Url . Unfortunately it is sending notification to email (which is default) but not the webhook url .The URL is tested and fine.
If anyone has faced this before please guide me.
Related
I am self-hosting the api management developer portal using a custom domain name via a Azure CDN and storage account. Authentication is provided using Azure AAD B2C. We have configured an authorization server to request access token using authorization code flow. When we access the managed site it correctly requests the access token and processes it using the reply url "https://apim-instance-name.developer.azure-api.net/signin-oauth/code/callback/name-of-auth-server", however, when we use the custom domain name it returns 404 not found when AAD B2C redirects the browser to https://custom-domain-name.com/signin-oauth/code/callback/name-of-auth-server". Is there something I'm missing?
Screenshot of redirected browser not finding reply url
Is there a way I can have a Python server send messages to a chrome extension, whether it be the content or background script?
I have a Python script making network requests that needs some cookies stored in my browser. I was trying to find a way to have the Python script send a message to the extension to refresh the page to get new cookies & send them back to the script.
In my Chrome extension is it possible to use Google Calendar's API watch method to receive push notifications instead of pollling without hosting my own server?
Can Firebase/FCM or chrome.gcm provide a solution? cloud based perhaps?
You can avoid the long polling but you'd still have to host a server even for the FCM.
I'd suggest you;
Go with Heroku, set up a free NodeJS dyno for your server. You can use the free MongoDB addon as your DB. Use the guide here to setup the server.
Setup FCM client in your extension using the guide here. Request the notification permission and get token on install or if you have a login system in your extension, after user has authorized. Send the token to your server and save in DB against that user's id or any other unique id that you can track from Calendar notification.
Use the Heroku app URL as target in Watch API. So all the notifications will be delivered to your Heroku instance.
When a notification is received from Calendar API;
Use any form of id in that notification and find the user's device/FCM token from DB.
Use that token as to and send message to that device. Handle the message on device as you want.
Calendar API -> Heroku Server -> FCM Server -> User Device
Means no need for 'long polling'. Your notifications will be delivered in realtime. Depending on the usage, you could also keep the Heroku instance free.
I would like to be able to send messages from an App Engine server to a Chrome extension. When the Chrome extension receives a message, it should increment the badge over the icon. Is it possible to send messages directly, or do I have to poll the server continuously from the extension?
You should look into the Cloud Messaging API, specifically chrome.gcm API.
This would be the best way to notify the extension from the server side, and can be a two-way communication channel.
Gmail blocks any suspicious activity, and kudos to them for that. An example of this is when you're configuring your SMTP module to use your gmail account for sending mail from your drupal 7 + SMTP module-enabled site. How do I enable gmail to accept mail from my Drupal site?
Here are the steps I use to allow Drupal + SMTP access to my gmail's SMTP server:
Note: disabling the "overlay" module may help with reading the output generated in step #6; so consider disabling it.
Install and configure the SMTP module for drupal. Configure for your gmail account. Instructions here
Prepare gmail to "watch" for new application access to your account.
Ensure that you've logged in to gmail using the same account with which you wish to associate your Drupal site
Visit https://accounts.google.com/DisplayUnlockCaptcha
You will be see instructions about how to enable another application to send on your behalf. You have 10 minutes after clicking [ continue ] to complete the next step.
The last field at admin/config/system/smtp is "SEND TEST E-MAIL" which doubles as an excellent SMTP debugger, btw. Enter your email address here and check enable debuging just below the field.
Click [ Save Configuration ] this will trigger the sending of the test email.
Watch the debugging output produced by SMTP, which the SMTP module places visually towards the top of the SMTP configuration page.
If you see send errors, review the output for corrective actions.
Hope this helps.