HTTP DCV Local http vs https Caching Error - centos

I'm trying to run AutoSSL to renew or issue a new SSL certificate on my domain. When I run it however I get the following issues on my domain.
I'm running cPanel 106.0.4 and i've tried re-installing both litespeed and cPanel itself. I'm also running CPhulk and ConfigServer Security & Firewall - csf v14.17
I try and delete the .well-known directory and AutoSSL recreates the pki=validation folders in the correct location /home/domain/public_html/.well-known/pki-validation/
I've tried rebuilding IP Address pools, pinging the domain locally to check the IP Address resolves correctly from the server to the server itself, rebuilding the Zone file for the domain.
1:04:07 PM Performing HTTP DCV (Domain Control Validation) on 31 domains …
1:04:07 PM WARN Local HTTP DCV error (mydomain.co.uk): The system queried for a temporary file at “http://mydomain.co.uk/.well-known/pki-validation/45DE0ED1146497E5E2019A467A25C8D6.txt”, but the web server responded with the following error: 404 (Not Found). A DNS (Domain Name System) or web server misconfiguration may exist.
What am i missing here?
Thanks
UPDATE 1
When I pull up http://mydomain.co.uk/.well-known/pki-validation/ I seem to get a different set of files than when I look up the https 443 version https://mydomain.co.uk/.well-known/pki-validation/ however this occurs on multiple devices and browsers implying its a server side caching issue perhaps?

Related

How to configure apache2 on Raspberry pi to serve https?

I am trying to use a Raspberry Pi 4 Model B as a small web server. It works fine for unsecured http, both within my home LAN and over the net. I have obtained a domain name and SSL certificate and key file. I am testing the server by accessing it within my local network using a browser and the Pi hostname. Unsecured http works fine, but making an https request results in a delay and then a "host refused to connect" message on the browser.
I have found conflicting instructions on the Web as to which Apache configuration file needs to be edited to include paths to the SSLCertificateFile and SSLCertificateKeyFile.
Within /etc/apache2 there are sites-available and sites-enabled subdirectories and more than one *.conf file, but apparently I have not edited the right one.
So, first, which is the correct configuration file to edit with the certificate paths, and second, does Apache produce a log file somewhere that would reveal any error messages produced by errors in the certificate?
I found a more complete set of instructions that showed how to add a port 443 virtual host to the default-000.conf file. It is working now.

DCOM got error "2147942405" from the computer x.x.x.x when attempting to activate the server:

I have a program on my computer that runs as SYSTEM and it is trying to launch an exe(opc server) on a remote machine x.x.x.x. But I get a DCOM error in my machine's eventviewer.
DCOM got error "2147942405" from the computer x.x.x.x when attempting to activate the server: yyyyy
I followed almost all the suggestions on the internet about opening dcomcnfg and adding users limits.default for launch and activation and Everyone,system,interactive,network from link (ftp://ftp.softing.com/pub/outgoing/opc/DCOM/DCOM-Settings-en.pdf) but nothing works.
Would anybody have nay other ideas on how to make this work.
According to MS Technet:
https://social.technet.microsoft.com/Forums/Azure/en-US/8bb5807f-73ba-4092-abc8-283d8fced6c4/request-a-certificate-from-certificate-service-fails-dcom-error-2147942405?forum=winserversecurity
With my VERY limited understanding of Certificate servers you may have one of the scenarios:
Client PC's are trying to connect to a Certificate server that no longer exists
Client PC's have a certificate that is valid but the Certificate server no longer exists
A Certificate server is broken
Clients do not have the proper authority to request the Certificate
I say this is limited knowledge as I am currently trying to remove AD Certificate services from a Domain Controller and I can see that in the System event log the exact same messages are being logged as I have stopped the Certificate services to asses the impact. If I get further information I will post back.

Google dataproc: Unable to access spark history page

I created a Google dataproc cluster. After logging into master node I started spark-shell then trying to access spark history page using
http://<external_ip_masternode>:4040
It get redirected to
http://<hostname_mastername>:8088/proxy/application_1487485713573_0002/
Browser is rejecting with error "DNS address could not be found." which is understandable.
Following are VM instance setting
Public IP type Ephermal
tcp:4040 opened in firewall
ip forwarding Off: Unable to edit this configuration
Following troubleshooting done but did not help
Telnet to :4040 -> Working
Access from Ubantu host/ browser Chrome: Getting redirected and name lookup failure
Access from Ubantu host /browser Firefox: Getting redirected and name lookup failure
Access from Mac OSX host /browser Safari : Getting redirected and name lookup failure
Access from Mac OSX host/ browser chrome : Getting redirected and name lookup failure
To view Hadoop web interfaces in Dataproc, it is recommended to follow the instructions for running an SSH-based SOCKS proxy: https://cloud.google.com/dataproc/docs/concepts/cluster-web-interfaces
If you follow the instructions there, it'll also have you run a separate browser session using your SSH tunnel, and sets hostname resolution to occur on the VM side of the tunnel. That way, all the links in the Hadoop pages will automatically work, since they all reference each other using internal hostnames, and intentionally avoid any dependency on "external IP addresses".
Using the SSH tunnel is also much more secure than opening up firewall rules to visit the unencrypted HTTP traffic directly coming from the Hadoop HTTP servers (if you accidentally open up your firewall rules too broadly, then other people on the internet will be able to access your external IP addresses, and even if you don't, attackers could see your unencrypted web traffic served up by the ApplicationMaster, HistoryServer, etc.).

HTTP error 508 from PERL script during redirection of requests from secure to non-secure server

I am getting a strange error in my file upload application.
1) Server 1: It is secure web server on port 443, which is accessible to public hosting a perl script
2) When this server get a request for cgi-bin directory, it will simple redirect the request to other web server (Server 2) running on port 80
3) The perl script in Server 2 will save the file in disk
Issue:
Above mechanism worked for a couple of hours later it has thrown Http error code:508
Observations:
If I directly hit Server2 on port 80, perl script successfully saving the files to disk. But If I directly hit Server1 on port 443, I am getting 508 error
When I first got the issue, I have restarted both webservers and it worked. But when I get the same issue second time, restart of servers did not help. The call to Server1 is throwing 508 error and requests are getting timed out.
ulimits and open files are in control.
If you experience this type of issue, please share your thoughts.
This strange issue has been resolved after moving dynamic service to other Virtual machine. This issue is no longer reproducible after changing the node.

Git Problem in Mac (Fatal Error)

I am setting up one git client on Mac (Using Source Tree). While committing the code it is showing the following error(please check the screen-shot). Any idea to solve this error ?
ERROR :
That generally happens when your server denies your connection. There are a number of causes for getting denied:
No/wrong SSH key (if the server uses SSH authentication)
Wrong port set up (the server doesn't expect connections from port 22, for example)
No/wrong username/password stored for the connection
Server set up wrong and still denying where it should be accepting
Check all your settings to make sure everything is right.
HTTP code 501 stands for "not implemented". If the git server works over http using another client, the configuration on the client side is incorrect, so make sure you have configured the correct server address, user name and password. (If the git server doesn't work over http on any clients, the server configuration is incorrect.)