Mesibo -- Turned off On-Premise But still the webhook call going to On-Premise IP - mesibo

mesibo
I turned on the On-Premise option.
Then my webhook call going to mesibo.js:73 WebSocket connection to 'wss://...:5443/' failed: from web-browser
ANd I turned it off due to network error.
Still my webhook call going to same Ip as before but not to mesibo webhook.But i didn't check the autofall back option first,But when turned off the on-premise I checked the autofall backoption and clicked in save option.
And all the users are showing as offline.
How can I get back on using the mesibo cloud again and all the users should be online.
The error looks like this

Related

Mesibo-How requests are routed when switched from Cloud server to OnPrem

We are evaluating mesibo for InApp messaging within our SaaS application. We would need OnPrem setup to comply to Data compliance requirements.
One clarity we would need on this regard is, when we switch from Cloud to Onprem setup still client side code continues to use https://mesibo.com url. In this case we believe all the traffic gets routed to our OnPrem server via Mesibo server.
Please confirm if this understanding is right? If so would there be any data residing on Mesibo server? This clarity is required for us to respond to our customers.
Thanks
No, once you enable On-premise, your client directly connects to your on-premise server. You can verify it using netstat utility. mesibo cloud will have no access to your data.
Refer to the following to learn more https://mesibo.com/documentation/faq/on-premise/#do-i-need-to-change-or-recompile-my-apps-to-run-with-mesibo-on-premise
Mesibo APIs support both cloud and on-premise. By default, it connects
to the cloud. However, if the app is configured to be on-premise, the
mesibo cloud will refuse to serve and will ask the client to connect
to an on-premise server, and will disconnect. Then onward, the client
will directly connect to the on-premise server and then all the
messages and calls will route to your mesibo on-premise server.

Unable to access website or SSH or FTP - Google Cloud and wordpress

I have a WordPress site hosted on Google Cloud, and was working very well.
With no apparent motive, stoped working and I can't access to it, neither the front panel or admin panel.
I can't access via FTP o SSH console.
The VM on Google cloud still running as far as I can see.
Errors I get:
When trying to access de website on Google Chrome:
ERR_CONNECTION_TIMED_OUT
When trying to access FTP via FileZilla:
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
When trying to access SSH:
Connection via Cloud Identity-Aware Proxy Failed Code: 4003 Reason:
failed to connect to backend You may be able to connect without using
the Cloud Identity-Aware Proxy.
i just want to update this issue.
The problem was that the memory quota.
I've increased the amounth of memory, restarted de VM and all went back to work.
Thanks
This page with SSH troubleshooting steps might be able to help you.
The issue could be solved by trying these troubleshooting steps. I think it is likely that the first one might be the cause of your issue since you mentioned it did work before.
Does the instance have a full disk? Try to expand it!
Is the firewall correctly setup, check your firewall rules and ensure that the default-allow-ssh rule is present.
Check your IAM permissions, do you have the roles required to connect to the VM?
Enable the serial console from your instance settings, connect and review the logs, they might give you some useful insights.

AWS SNS to notify a locally-running CLI application

AWS SNS can push to http, email, SMS, lambda, "device and mobile application".
Is there a way to get it to push to a locally-running CLI application?
I can imagine that maybe it is possible to register an EC2 server as a "device" and the CLI as the "mobile application". Couldn't figure out any docs about this.
Edit: or perhaps register an EC2 server as IoT and push sns to IoT device?
No. Sort of.
Amazon SNS needs to send a message to "somewhere" that wants to receive the message. So, you could run a web server that is Internet-accessible and SNS will send the message via HTTP to that endpoint.
Mobile applications also have endpoints provided by Apple/Google/Baidu that will then forward messages to a mobile device. So, they are also listening for a message.
Bottom line: You need something that is listening for a message.
You can use ngrok for this. This answer should solve your question perfectly.

Google Cloud Messaging - Error [401 Unauthorized] on server only

My website (in php) should send Push notifications to an Android app. It used to work fine for some time, and suddenly stopped.
When I checked the return error code, it was 401 (Unauthorized)
I was using 0.0.0.0/0 as the allowed IPs. Seems it is no longer allowed after a grace period. So I set my DSL spool IP address and my server IP address. I have a dedicated IP to my cloud server (On RackSpace).
Then it worked in my localhost, but not on my cloud server. I also confirmed that my server outgoing IP is same as my server dedicated IP.
I had to set my Servers IPv6 address to Allowed IPs. Then it worked again - perfectly
[On Google Developers Console - API Credentials settings]
I'm documenting this for it would be helpful to someone else too.
Change the allowed IPs in your google console api project..

microsoft azure smtp email relay setup

We are migrating from a dedicated server with a local virtual SMTP server to Windows Azure. As far as I can tell Windows Azure does not allow a local SMTP server to be setup in IIS. The SMTP Server option in the management console is missing. How would I setup an email relay so that I can have a .net web application send emails from a Windows Server 2012 virtual machine in Azure?
This is more like corollary to what #mcollier has stated. Given that you are already on Azure and you get 25,000 free emails (there are higher plans as well) with your subscription as well.
You can configure a Virtual SMTP server which relays to the sendgrid services. For the development perspective you will have the view of using your own SMTP server / service. Setting up a sendgrid based service is explained in this link.
I have used sendgrid earlier and my experience with this was amazing. As #mcollier has pointed out, using services like Sendgrid will give good chance of staying away from spam problem, if you try to setup and use the SMTP service of your own because of the reverse lookup etc.
PS: The above Virtual SMTP Server can be replaced with Amazon SES, which is equivalently a good service. Check out more info here.
First, assuming you're using a Windows Azure IaaS VM. Correct? If so, I think you need to enable that role/feature in Windows Server.
Second, why the need to send emails from that specific server? Would a service like SendGrid work? One problem people sometimes have with email servers in Windows Azure is the domain of your service (something.cloudapp.net) does not match your vanity domain when a reverse DNS lookup is performed. This could cause the email to be flagged as spam (since you don't technically own the sending domain, something.cloudapp.net).
I developed an direct relay application using the normal RFC email commands and lock that on my application, but strange that some test emails get delivered using the relay on windows AZURE VM, and all other mails are not getting any bounce response, and making a sense that every email is being delivering,
This is strange behaviour on azure vm.
so it means you can't send email using azure vm as a smtp mail server, if like to test then simply download promailer marketing manager from jsmtp.com

Resources