Intermittent certificate error when accessing server URL - networking

I have an application running in a k8s cluster in AzureChinaCloud behind an ingress (internal load balancer) which in turn sits behind an application gateway with a public ip. The DNS point the URL to the public ip and all nslookups are giving back the correct address. The endpoint is HTTPS and the certificate is good and in date and correctly configured on the listener of the application gateway.
However 9 times out of 10 when I try the URL I am getting the below error
"Secure Connection Failed
An error occurred during a connection to blablabla SSL received a record that exceeded the maximum permissible length.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified."
However intermittently it does load okay. I cant match the failure timestamps with any failed requests in the app gateway logs. I ran a wireshark and I am seeing some errors like
[TCP Out-of-Order]
I see some RST messages from the client to the server
I also see some HTTP/1.1 403 Forbidden messages but I see some of these during the successful attempts also

If you create a website in china cloud you apparently need to register it with ICP. Below are the details I got from Azure support
Problem Reason:
There seems to be an issue with ICP registration.
More details about ICP registration:
According to the ICP filling requirements of China's Ministry of Industry and Information
Technology (MIIT) and China Public Security Ministry, a website is accessible only if the registration is completed and the filled information is accurate.
In addition, the access should be suspended if any prohibited content is published or disseminated.
If the website has not bound a custom domain, please bind your own custom domain with ICP filing for your websit

Related

unable to send API request to Solana devnet

I'm doing the following tutorial of creating tokens on Solana.
https://spl.solana.com/token
and it seems that all requests to Solana devnet are failing
$spl-token create-token
Creating token 2rxgzZ1tk692aZJXDz8NhTkVXQWB396Z3L21nTUYWCFi
error sending request for url (https://api.devnet.solana.com/): error trying to connect: invalid certificate: UnknownIssuer
I'm not so much of an expert when it comes to network, but i thought it was permission issue in firewall as I am currently working on this in corporate environment.
but as I tested with telnet, it doens't seem like a firewall issue
147.28.33.107 is an IP address of Solana devenet network.
telnet 147.28.33.107 80
I have the similar problem but I sorted out by specifying the path to my-keypair.json.

'Invalid hostname' response from http.sys

We have web service running hosted on an OwinHttpListener (http.sys behind the scenes). Whenever we send requests to the app on the IP address, it responds with 'Invalid hostname'.
After much trawling of stack overflow and google, im not really any closer to a solution. The requests are getting through to http.sys, as i can see them in the HTTP error log. I can log onto the server in question and access the service locally (using localhost or 127.0.0.1) and i can use the server name to successfully get through, the only failure condition is using the servers IP address.
Ive tried the following:
Ensure the app is listening on all interfaces (http://+:8080)
Ensure IIS is not trying to use the port (it isnt)
Ensure windows firewall is configured to allow traffic on that port (it is)

Can't place message in MSMQ on server in DMZ using HTTP

I can't place a message in a non-transactional MSMQ on a server in our DMZ using HTTP. In the IIS logs I'm getting: 2013-05-15 20:29:54 W3SVC1 192.168.32.XXX POST /msmq/private$/newprivate - 80 - 170.115.XXX.XXX - 403 4 5
Based on the 403 I'm thinking that I don't have permission to the queue (or the MQISE.DLL)
I've added permissions to the following accounts: IWAM, IUSR, NETWORK, NETWORK SERVICE and I still can't access it. It works if I add a message on the box.
Any suggestions? Thanks in advance.
Are you sending from a transactional queue to a non-transactional queue? This will drop the message. Turn on negative source journalling for the message. Set the UseDeadLetterQueue of the message to true.

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

SoapUI and web service testing with windows authentication

Blockquote
I'm trying to test an already deployed web service through SoapUI. The service URL is https://hostname:82/Service.asmx. I modified the test Endpoint to reflect this. Web requests go through a proxy that uses Windows Authentication.
First I attempted to run the test directly but without success. All I got was an error:
401 - Unauthorized: Access is denied due to invalid credentials
Next, I entered proxy details and domain username/password into SoapUI proxy settings. This creates another error:
status# HTTP/1.1 502 Proxy Error ( The specified Secure Sockets Layer (SSL) port is not allowed. Forefront TMG is not configured to allow
SSL requests from this port. Most Web browsers use port 443 for SSL requests. )
I wasn't really paying attention to this until now so I ignored the error and went on to install Burp Suite hoping that this would help with Windows Authentication. I got the Internet working through Burp Suite but soapUI still doesn't do anything and I can't run any tests. This time the error is a bit different:
XML Parsing Error: syntax error Location:
https://hostname:82/Service.asmx Line Number 1, Column 1:Burp proxy
error: failed to connect to IP.
What am I doing wrong? :)
Figured it out in the end. I configured Burp proxy the wrong way. Instead of redirecting to my WS server, I was redirecting to our internet proxy which of course didn't know what to do.

Resources