405 ERROR: Requested resource does not support http method GET - asp.net

I know there are similar questions like this, but mine is unique. I'm running IIS 7. Initially I was receiving this error when POSTING/GETTING directly to the server in question. I read through answers on this topic and removed WebDAV from my config files, even though WebDAV wasn't installed on the server in question, and stopped receiving the 405 errors. The issue I'm having now, is when I access the server publicly and go through our companies firewall I'm receiving the 405 errors again. We have a public address that routes directly to the server in question. Any idea why this could be happening?

Related

Docusign Connect / webhook error: The underlying connection was closed: An unexpected error occurred on a send

Not sure if this is a Docusign or ngix question.I'm working on integrating an application with Docusign and I keep seeing this somewhat vague error below in the Docusign Connect logs. In our nginx logs I see that a POST to our application's /webhook endpoint was attempted but doesn't go through. I've specified TLS 1.2 and have tried increasing our nginx timeout but that doesn't seem to fix it.
One theory I have is that our server's certificate isn't chained to a Microsoft trusted CA but I would expect a different error if that was the case.
Any help or guidance would be greatly appreciated.
This most likely would require you to get the IT folks managing this server and networking involved. And yes, they may need to install a certificate, but other errors can be related to the firewall blocking certain requests, an anti-virus blocking requests and even DNS related error preventing the HTTP request from being sent and received by the server.
We highly recommend to use a public cloud for Connect and we have plenty of examples how this can work, while still having your code run on your own IT server.

API request and Error in curl::curl_fetch_memory(url, handle = handle) : SSL certificate problem: certificate has expired

I was running the code for months without any issues, and couple days before.
GET(url="myurl", query)
Today I've got an error
Error in curl::curl_fetch_memory(url, handle = handle) :
SSL certificate problem: certificate has expired
The SSL cert on the site is active and ends in a year.
Also the same GET request is working via browser....
What is the issue? 🤷‍♂️
Try testing your server with this tool: https://www.ionos.com/tools/ssl-checker and see if it says that it is "not installed correctly".
If you find that it has been working historically but recently stopped, you likely have an invalid chain of trust. Recently, a common root CA certificate expired. Your server may be using this and sending it as part of it's chain of certificates it sends to clients. If that is the case, and it is this recently-expired root CA, your fix will most likely look like removing that root certificate from your bundle. So you'd include the intermediate certificates still, but exclude the root. You can then use these tools to revalidate if things are setup correctly.
You can also see the chain and some of the validity information using this tool: https://www.sslshopper.com/ssl-checker.html

Access website using server name instead of www

I am new to IIS, setting up servers and load balancer so please do not mind my ignorance.
I have an old website, say, www.mywebsite.com.
There are 3 IIS 6.1 web servers on which my ASP.NET code is hosted.
Lets call them web01, web02 and web03.
They are identical in configuration like OS, etc.
There is a load balancer which handles the requests coming in from the clients through www and routes it to the respective server based on whatever algorithm is put in place.
However, we were able to send requests directly to individual servers like this web01.mywebsite.com for all 3 servers.
I do not have access to the load balancer.
Recently there were some problems with the web02 server so the client took it out from the load balancer.
We then reinstalled IIS and now, when we are trying to access the server using web02.mywebsite.com, it is throwing 404 - Not Found error.
I am able to open the website from inside the server using www.mywebsite.com and I am able to see that the requests is catered by the web02 server.
However, from inside the server also web02.mywebsite.com is throwing 404 - Not Found error.
I am sure I am missing something in configuration at the IIS level but not able to figure out.
I tried searching on the internet but they all gave me generic solutions.
Please help.
Thanks in advance!
I was able to get this resolved on my own.
Strangely there was not a single answer or comment to this question.
I will try to answer so that others might also benefit.
There were 2 things that were required, out of which 1 was already present in my case:
In the hosts file, the mapping of IP address of the server to the actual name of the server should be present (This was there in my case)
In IIS, under bindings, I removed the host name i.e. www.mywebsite.com.
I was able to figure this through the posts here and here although they did not give the answer directly.
Hope this helps others.

502 error monitoring in Nginx server

I have a Linux server running Nginx and from time to time it starts throwing a 502 error when trying to access it throw HTTP, and after a while gets back to normal.
I've checked the different logs (Nginx, PHP and MySQL) and didn't find anything that could help me find what's causing this.
Any idea where I should look or if it's possible to set any logging/monitorinh tool to help me out?
Thanks,
502 is a Bad Gateway error. You may want to use a log monitoring tool to see these types of errors. You may also want to send the PHP errors to see if they are generating fatal errors at the same time. I personally use Loggly for this purpose, but you can use other tools available in the market.
Also, I would recommend logging Nginx as JSON, and adding to the normal metrics, the uptime for the upstream servers, so that you can see if the 502 errors are also correlated with deteriorating performance.
If you haven't read this already, I recommend starting here:
https://www.nginx.com/resources/admin-guide/logging-and-monitoring/

Import from wordpress to wordpress

I'm trying to import all my stuff from videomarathon.com/dk to videomarathon.com/se (posts etc.)
I'm using wordpress importer.
When uploading the exported file, it shows me this error:
Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 1333795156
Varnish cache server
Does anyone know what it means?
Is there anyone who might know another plugin for importing?
I'm using multiple sites, so maybe that's an issue?!
Thanks!
HTTP Error 503 - Service unavailable
The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.
503 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:
Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '503'.
Fixing 503 errors
The Web server is effectively 'closed for repair'. It is still functioning minimally because it can at least respond with a 503 status code, but full service is impossible i.e. the Web site is simply unavailable. There are a myriad possible reasons for this, but generally it is because of some human intervention by the operators of the Web server machine. You can usually expect that someone is working on the problem, and normal service will resume as soon as possible.
Please contact the system operators of the Web site (e.g. your ISP) to determine why the service is down. They will be in a much better position to help you than we are for this type of error.
Talk to your web host; it's an error at your web host one.com. The WP import plugin will work fine once the host problems are fixed.
And there's already an answer here to the same quesiton: Varnish: Guru Meditation

Resources