I have hosted my WP app in AWS EC2 and is using GoDaddy DNS to point it to my domain. I received and email from GoDaddy stating that my site is blacklisted by McAfee as Malicious. Please see the image:
Now, when I try to access my website Google shows an error page with the following content : DNS_PROBE_FINISHED_NXDOMAIN. Is this because my site is blocked due to the McAfee blacklisting. Any help on this is highly appreciated, Thanks in advance.
DNS_PROBE_FINISHED_NXDOMAIN means that your domain is no longer pointing to your server.
to troubleshoot you may use these steps:
check your domain resolve status via this tool https://dnschecker.org
if NOT resolved at all register a Cloudflare account then change name servers in your registrar panel to NS provided by cloudflare.
make sure that all DNS entries are like original zone.
wait for propagation and recheck https://dnschecker.org
restart your home router and run this command on windows CMD ipconfig /flusdns
if you are on Debian/Ubuntu run sudo /etc/init.d/networking restart
You can try below solution to fix DNS_PROBE_FINISHED_NXDOMAIN issues.
Release and Renew IP Address
Restart DNS Client Service
Change DNS Servers
Reset Your Browser
Disable VPN and Antivirus Temporarily
try this post for complete info:- DNS_PROBE_FINISHED_NXDOMAIN
Related
I changed my VM instance from "F1-micro" to "E2-micro". When I then restarted my machine, I couldn't access my webpage using the domain name, the webpage just shows an "Error 521" code - showing that my browser is working, CDN is working but the host has an erorr. When I paste the VMs IP address into my webpage, however, it show's the "Apache2 Debian Default Page".
Can somebody please help me with this?
The Error 521 message is caused by one of two situations:
First, check whether your WordPress site’s server is down. Even if everything else is configured properly, if your WordPress site’s server is offline, Cloudflare simply won’t be able to connect.
Second, your web server might be running fine but blocking Cloudflare’s requests. Because of how Cloudflare works, some server-side security solutions might inadvertently block Cloudflare’s IP addresses.
Cloudflare is a reverse proxy, all the traffic coming to your origin server will appear as if it’s coming from a small range of Cloudflare IPs (rather than each individual visitor’s unique IP address). Because of that, some security solutions will view high traffic from a limited number of IP addresses as an attack and block them.
Please check this link out in order to fix error 521 for Cloudflare and WordPress.
Turns out this problem was caused by my having installed the Debian Apache server package and it is causing collisions between it and the Apache shipped in the stack. Bitnami Stacks are completely self-contained and run independently of the rest of the software or libraries installed on your system.
So to fix this, all I had to do was run the following commands:
sudo systemctl stop apache2
sudo /opt/bitnami/ctlscript.sh restart
I'm trying to connect WordPress instance on google cloud with the custom domain but I'm having this error
This site can’t be reachedquotivy.com refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
What I found it wired is that the domain is working on Tor browser and not working on Chrome and Safari, and I tried to take an online screenshot from it and it's working & I ping the domain and seems working too! not so sure what to debug or do to fix this bug!
This is a sample URL: https://quotivy.com/rumi/when-the-world-pushes-you-to-your-knees/
How it looks like on my browsers:
Custome DNS on my google cloud
If you have moved the site recently then check in your database (either domain.com/phpmyadmin or SSH if Cloud SQL) for references to the old domain and update to the new domain. This includes moving from http to https
In GCP Compute Engine VM Instance settings, make sure to allow http and allow https traffic. You may want to assign a static IP in GCP Console > VPC Network > External IP addresses
Lastly you may need to update etc/apache2/sites-enabled/000-default.conf to make sure your servername matches your WordPress domain name
Forgive me here, I am largely post-technical for 10+ years and taken this as far as I can. I can probably take any advice and run with it, but may ask for some specifics to help if troubleshooting tools or commands are required. So please forgive that too.
Background:
Yesterday we could hit site URL after restarting VM hosted on Google Cloud. Sometime overnight, the URL was inaccessible.
Message:
This site can’t be reached <URL> refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
Troubleshooting:
can load using IP.
The technical guys (3rd party suppliers) insist they have not made any changes. My team have not made any changes.
The domain is still valid (it renews tomorrow)
The domain is used for the DEV environment with DEV as a prefix hosted on another VM.
Looking at firewall rules, all the rules with the proper tags appear to be set up correctly for HTTPS with appropriate IP (0.0.0.0) and port 80.
Many thanks in advance for your help. When I find the answer, I will post it here.
RESOLVED:
ROOT CAUSE:
During setup on GCP, the team forgot to link the reserved external IP address to the VM. As such, the external IP address was ephemeral so after a reboot of the server, Google issued a new external IP for the VM.
SOLUTION:
Reserve a static external IP Address and link it to the VM or promote an existing ephemeral external IP Address.
https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-ip-address
Just trying to set up SSL https for my site, using the Bitnami Tool bncert-tool. It shall automate the SSL setup by naming the domain. Unfortunately, I get the message
Warning: The domain 'mypage' does not resolve, please fix its DNS entries or remove it.
Press [Enter] to continue:
Thing is, I can get to the page via domain name and the IP. So no Problem on that side.
I have no clue! I have set up an elastic IP in EC2 and connected the domain in Route53 by adding the dataset. Has some faced the problem before and cases.
From the warning message, 'mypage' is not a domain. Actually have to enter in the full domain path such as
www.google.com
or
google.com
Good luck.
I created an AWS server and installed wordpress with an elastic ip address and verified that the default website was up and running.
I wanted to make a backup image at that point so that I could use it as a beginning point for other websites. However, after getting the AMI running and attaching the elastic ip address to it, I got an "connection refused" error. I can both SSH and FTP into the server, but the wordpress site is offline. I then switched the elastic ip back to the original server and got the exact same issue.
I'm guessing that this is a "change of ip" type error(?) (although, when I've seen that before, the connection has never been outright refused... it usually allows at least access to the admin area of the website) but I thought by using an elastic ip address that I would avoid that. I'm also confused by the error in the first server, since the database still has that address.
Any ideas about how to troubleshoot something like that? Is there anything else that it could be?
Well.... I missed something vital.
Using an AMI works just fine with an elastic ip address. I had forgotten to make sure the webserver (httpd) and mysqld were running with :
service httpd restart
and
service mysqld restart
What made it click was reading that the main reason for this error is that there is listener to the incoming data.
Duh.