when scheduling a Meeting from the Team client. We receive a NDR complaining about “Remote Server returned '550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP. Scheduling from outlook web and client works fine without any issue.
Related
I'm deploying my .Net 6, Blazor Server site for the first time on shared hosting. It's all seems to work so far bar two things.
In the browser console (Chrome) I get an error:
Error 1
blazor.server.js:1 WebSocket connection to 'wss://www.mysite.co.uk/_blazor?id=qW5eCRVc_HbgSWt8iESawA' failed:
Information: (WebSockets transport) There was an error with the transport.
Error: Failed to start the transport 'WebSockets': Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled.
Warning: Failed to connect via WebSockets, using the Long Polling fallback transport. This may be due to a VPN or proxy blocking the connection. To troubleshoot this, visit https://aka.ms/blazor-server-using-fallback-long-polling.
The page seems to work & I've added all the CSP entries I can find so that's the only error left.
Error 2 is when I call Braintree to capture a payment. That's the only Braintree call & it works fine locally.
Transaction.SubmitForSettlementAsync(transactionId, amount)
gets an exception : The request was canceled due to the configured HttpClient.Timeout of 60 seconds elapsing.
I have no idea why that is & assume is blocking is call. Any help would be appreciated.
For this warning:
Warning: Failed to connect via WebSockets, using the Long Polling fallback transport. This may be due to a VPN or proxy blocking the connection. To troubleshoot this, visit https://aka.ms/blazor-server-using-fallback-long-polling.
see: https://learn.microsoft.com/en-us/aspnet/core/signalr/publish-to-azure-web-app?view=aspnetcore-5.0#configure-the-app-in-azure-app-service
For apps hosted without the Azure SignalR Service, enable:
ARR Affinity to route requests from a user back to the same App Service > instance. The default setting is On.
Web Sockets to allow the Web Sockets transport to function. The default setting is Off.
In the Azure portal, navigate to the web app in App Services.
Open Configuration > General settings.
Set Web sockets to On.
Verify that ARR affinity is set to On.
I'm facing kind of SMTP mail problem sending through the application using coding as below
SmtpClient SMTPServer = new SmtpClient("smtp.office365.com");
SMTPServer.UseDefaultCredentials = false;
SMTPServer.Credentials = new System.Net.NetworkCredential("xxx#xxx.org","xxxxx")
SMTPServer.Port = 587;
SMTPServer.EnableSsl = true;
So been using this method 2 years ago until recently where we face email not able to send out intermittently with error message "Smtp Error: Failure sending mail". There are times where emails could send out with only average 12 emails per day. Plus, the sender email address from the application is active with correct credential login and password.
I checked our Windows 2008 R2 server and tested with our disabled firewall on server. Problem still persists. And there were no patches update to the server as well.
Is there anything to do with authentication type level? Or certain communication protocol conflicts? How do I check further to determine the root of cause? Our firewall already allowed the port 587 to send out.
There could be many issues to check. You say that the application is sending emails as a "client" to an Exchange 365 SMTP server to sent onwards, that's what the example looks like.
Check that Exchange is not rejecting the request. Microsoft can be very picky about application clients connecting directly. Look in the logs.
Check that your email application client uses TLS 1.2 or above. Many SMTP servers will reject requests below that level.
Exchange might be insisting on a STARTTLS for negotiation on credentials, so check if that is the issue.
Check that the application client is whitelisted in MS Exchange 365 if it is rejecting requests.
Check that the user you are connecting as has privilege to accept connections from remote clients. I often lock this down to prevent brute force password attacks.
Normally I would test all this out on the command line first. Get an email client for your OS like:
sendemail-1.56 by Brandon Zehm <caspian#dotconf.net>
Which is very good at initiating a connection to a remote server. Test from your application client email server and see what happens.
When connecting to a local instance of the bot through a proxy and ngrok, I am able to receive responses using DLS client. However, when testing with the app service I receive no responses back and the following error:
"Error ConnectionFailure : Connection was closed by the remote host. Error code: 1000. Error details: Exceeded maximum websocket connection idle duration(> 300000ms) SessionId: 2ee9810a2916418a93dc1e978c49566b"
I have tried to restart the app service, ensured I have checked the "Enable Streaming Endpoint" box and toggled "Web sockets" to On, and even tried creating the app service. Looking at the app service logs, The GET request to the appservice returns 404, the bot receives a request and invokes StartWebSocketAsync but gets a 400 error and completed the request with http 400. There are no other exceptions being thrown, and locally everything seems to be working fine.
Any pointers would be appreciated.
Thank you!
Hello Google folks monitoring the API questions.
Today our API requests to the Contacts API are being blocked with 503 Service Unavailable and this message in html suggesting to do CAPTCHA:
Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot.
The block will expire shortly after those requests stop. In the meantime, solving the above CAPTCHA will let you continue to use our services.
We checked our API console and we're nowhere close to reaching our daily API request quotas. Why is this happening?
And how is a service supposed to do CAPTCHA? It's communicating using API from our servers but those messages are intended for a human using a browser.
I have asp.net MVC 3 application that sending various emails such as client registration, activation etc
Currently using smtpclient and smtp server authsmtp.com. In last 3 months there was number times application used to hang when sending email and smtp is not responding.
I am now required to review the process and improve with following improvement.
1.) Application should not hang when smtp server is not responding.
2.) Queue email for later delivery if smtp server is not available. Re-try delivery for next 24 hours
3.) Add extra logging for email queued, sent or failed (After 24 hrs)
I would like to know what will best option to implement the above requirement.
The application is hosted in windows azure environment.
I thought to use MSMQ as provides message queueing and I can log the details once each task is started and completed.
Reference : http://dotnetslackers.com/articles/aspnet/Sending-email-from-ASP-NET-MVC-through-MVC-and-MSMQ-Part1.aspx
The problem is that MSMQ is not supported on windows azure.
Please advise ?
Thanks
There is an example on WindowsAzure.com that covers a similar topic as this http://www.windowsazure.com/en-us/develop/net/tutorials/multi-tier-web-site/1-overview/