I configured the SMTP setting om my DNN 7 siteand everything worked fine for weeks. I tried to send a newsletter today and discovered that there is a problem with the SMTP (even though i have changed nothing). I checked the configuration and verified that it hasn't been changed. And indeed it hasn't. I tried a few email accounts that i have and received the same error time and time again. Here is the error:
There has been an error trying to send the test email. The error is:
There is a problem with the configuration of your SMTP Server. Mail was not sent.
Any ideas?
Well, I checked the error and it appears that i used all my allowed emails out by the email server. I guess this is one of the first thing i should have checked...I suggest you to do that if it ever happens to you :)
Related
I have a Windows desktop client which connects to Identity server using Authorization code + PKCE.
It seems to work perfectly fine if I run it through visual studio.
I have then installed the desktop client on my own machine and it connects to Identity Server, displays the log in screen and then logs in fine.
For some reason though, when I install that same desktop client on a server, or even the same server that it sits on, then it displays the login screen but when I enter credentials and click on login, then it displays the following HTTP 400 error....
This error (HTTP 400 Bad Request) means that this program was able to connect to the web server, but the webpage could not be found because of a problem with the address.
I don't understand what could be going wrong or what could be different between the desktop client sat on my machine or the one sat on a server.
I would appreciate whatever help I could get on this.
The main thing I can see is that it doesn't even seem to hit my Identity Server 4 LogIn post controller method (but does hit the Get method as expected).
Note - I am using an In Browser control on Windows so it is Identity Server that seems to be the post and erroring out with the HTTP 400 error.
We fixed it by implementing ValidateIssuerName = true (previously was false) and everything else that was needed with that.
Previously, ID4 on discovery mode was giving its own URL, whereas we updated it to provide the URL of the gateway.
I am developing a .Net Core (3.1) web application hosted with IIS 10. When I am trying to use SignalR on localhost, I am able to connect totally fine and receive messages from the backend, but after I publish it to IIS, I get the error: "Server returned handshake error: Handshake was canceled." In the client logs on Chrome's console, I get the message: "Information: SSE connected to http://myserver.com/MyApplication/output" before I get the error described above (which you would think means that I connected successfully)...
I have seen other posts where people have suggested that I have to enable webSockets on IIS, and I have already checked the my site has this enabled.
I have also seen people suggest to try using the longPolling argument in the withUrl function when creating the connection, and this has not helped either.
I have also added SignalR Event Log Trace Listeners to my web.config file, and the only warning I get that might be related to this issue is that I get a warning from the .NET runtime that reads "Failed to determine the https port for redirect." I am not sure what this means or if it would be related to SignalR, but as this also appears to deal with Middleware, it might be significant.
One thing that I thought might be related is that my site is just one of multiple hosted on this server, so that when I am running locally, I can use the following to connect to SignalR:
hubConnection = new signalR.HubConnectionBuilder().withUrl("/output").build();
But because of the way this site is deployed on my server, I have to use this:
hubConnection = new signalR.HubConnectionBuilder().withUrl("/MyApplication/output").build();
when I deploy the site or else I get a 404 error...
Would there be any issue there? I noticed when inspecting the network requests that on localhost, the URL to connect with the socket is "wss://localhost:44315/output?id=..." and I get the "Status Code: 101 Switching Protocols", but after I deploy, the url that is used is "http://myserver.com/MyApplication/output?id=..." and I get a "200 OK" just before receiving the error described at the top. Why does wss get used on localhost but http is requested from my client when I deploy?
FINALLY discovered the issue after days of debugging... The reason I was getting a "101" response on localhost and not when published is because 101 is basically the server (IIS in my case) saying "I support web sockets". I realized that because I wasn't getting this when published, web sockets were probably not enabled in IIS. It was weird, however, because I went into IIS manager and it said that web sockets were enabled, but after much more research, I found that you also have to go into "Server Manager" and enable it as well (see here https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-websocket-protocol-support and follow step by step instructions). I did not realize both were required.
I am using Vtiger CRM on localhost and for single machine only,
This time when i tried to connect Vtiger on other computer through http://ipaddress_of_1st_machine:8888 then getting "Illegal Request Error".
When i am clicking on "GO BACK" option which is coming at bottom of Illegal Request Error Box, then it is rendering me on home-page but again after clicking on every module or activity same Illegal Request is getting. Means not able to access 1st machine's database
Kindly help me out or tell me what to do to access that, I tried my best.
Thanks
From vtiger 6 onwards, there is a security check added to enforce that the value of the $site_URL variable under config.inc.php is same as the url you are trying to access.
Since you have installed it from localhost, i am guessing it is set as http://localhost/[something] and you are trying to access http://[server-ip]/[something] which is why you are getting the error.
To resolve, you just need to change the localhost to the [server-ip] in the $site_URL variable in the config.inc.php
Background
We currently have a SilverLight form that posts data to a second common form that multiple applications use, which then runs the need business logic to place the data into a database.
We have several national and international offices where this form is used.
There is one office location (CO) where this form is consistently producing intermittent error messages and based off log data, it is only happening in this office.
Error Symptoms
Initially users will typically report that there is an error and when I log into their machine using MS Communicator, 80% of the time it would start working.
I started installing Fiddler on their machines to try and capture more information but 100% of the time I did that, the form started posting successfully. The users being resourceful, simply start Fiddler anytime the form doesn't post and it works fine.
I also asked users to go through Citrix which is hosted in the TX office and the form posts fine.
Error Details
I used OPNET to better monitor the traffic and I found that when user's simply open IE the authentication handshake fails.
Client => Server = 401
Client <= Server = Authentication Token
Client does not respond
When we use fiddler, the handshake is successful.
The error returned by SilverLight was a very generic [HttpWebRequest_WebException_RemoteServer] message.
Question
What would cause the handshake to work sometimes by itself, always with fiddler and CITRIX, and sometimes it doesn't.
I am facing some weird problem, I have installed the SMTP server on my AIX box and I am successful to send email using the following command:
mailx -s "Hola Mundo" email#domain.com < /tmp/test.txt
But when I am sending the email using the javamail api I am getting following exception, could you help me how to resolve that.
javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
javax.mail.SendFailedException: 550 5.7.1 <email#domain.com>... Relaying denied
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:632)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:306)
at SendMailUsage.main(SendMailUsage.java:59)
and I am sure my email address is perfect one.
Check out the RFC 2821 (Simple Mail Transfer Protocol), especially the part about STMP replies: https://www.rfc-editor.org/rfc/rfc2821#section-4.2
Status reply starting with 5xx indicates a permanent error. In your case your SMTP server is not configured to route mails to your given destination address.
Issue has been resolved by modifying the sendMail.cf file on the server side. My aix admin informed me that it was due to some DNS issue, will update the solution as soon as I hear from him