The website domain is www.myhomeetal.com. I tried to view the logs via SSH on the server, this is what I got.
Got error 'PHP message: PHP Warning: Invalid argument supplied for foreach() in /opt/bitnami/apps/wordpress/htdocs/wp-content/themes/revo/lib/widgets.php on line 714\n'
and this
Certificate and private key localhost:443:0 from /opt/bitnami/apache2/conf/server.crt and /opt/bitnami/apache2/conf/server.key do not match
AH00016: Configuration Failed
I attempted installing an SSL certificate when I noticed the site was offline. Could that have caused the whole site to be offline.
Hi Bitnami Engineer here,
It seems that Apache is running properly now but the DNS is not properly configured. As you can see in this online tool, the ec2 and www.myhomeetal.com are set properly to the machine's IP but the myhomeetal.com domain is not
https://www.whatsmydns.net/#A/ec2-18-191-15-113.us-east-2.compute.amazonaws.com
https://www.whatsmydns.net/#A/www.myhomeetal.com
https://www.whatsmydns.net/#A/myhomeetal.com
You just need to configure myhomeetal.com to point to the machine's IP
Happy to help!
Related
I'm migrating a bitnami wordpress site from AWS lightsail to GCP.
The AWS's setup includes a purchased wildcard SSL. When I set up the loadbalancer in GCP, I opt for Google's SSL instead.
I got this error Error code: SSL_ERROR_NO_CYPHER_OVERLAP when I access from the loadbalancer's IP. The VM is working fine and I am able to access it with it's own external IP.
The domain is still pointing to AWS's server. I wonder if the error is because I have not pointed the domain to the load balancer's IP?
I'm hoping to gain some clarity first before I update the domain's IP. I want to avoid situation where it does not work after I make the switch.
Thanks
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
Hello fellow developers,
I was following this guide (https://medium.com/#federicodeicas/how-to-setup-your-server-with-freenom-tk-82c7302bcce4) to setup/simulate an Nginx server running on Ubuntu in VirtualBox with bridge enabled. My first attempt was a success.
However, when I try to redo the same steps for a 2nd domain on a second ubuntu server in a different virtualbox environment with the same public IP address (both running on the same machine), I get a "This site can’t be reached" error, despite successfully obtain the new SSL certificate for the 2nd domain
What could possibly be the problem?
thanks in advance
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
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