fastrak
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] Same Ip Address for All OrdersI just got this from Hostgator:
Hello,
Thank you for contacting Hostgator Support.
At this moment I was able to review the issue and information provided via the email responses and you are correct, the issue is taking place because of the current update from ea3 to ea4. This issue has been address and we currently have a team of Sr. administrators working on resolving the issue, allow us some time in order to implement a fix on the whole shared server environment in order for the functionality of your site to continue as it’s intended.
If you have any further questions or concerns please let us know via this case escalation or contact us via chat or phone support.
Best Regards,
Josue Z.
HostGator.com LLCWill do. Thank you for the help.
I ran a php script already and here are my observations:
For SSL:
REMOTE_ADDR= 71.9.168.27
HTTP_X_FORWARDED_FOR= 192.185.152.20
HTTP_FORWARDED=
HTTP_CLIENT_IP=For Non-SSL:
REMOTE_ADDR= 71.9.168.27
HTTP_X_FORWARDED_FOR= 71.9.168.27
HTTP_FORWARDED=
HTTP_CLIENT_IP=I am seeing on Hostgator sites. Hostgator updated their EasyApache to 4 a few weeks ago. Now my site with sucuri wp plugin is logging login attempts with the server ip address. I noticed that when I look at the x_forwarded_for it shows only the server IP when I am connecting with https so I think it is a hostgator configuration error. I looked for the Forwarded variable but it is blank.
Forum: Plugins
In reply to: [WooCommerce] Same Ip Address for All OrdersI am not an expert at this but I think it is a problem with the update that Hostgator did. It looks like it started when they upgraded EasyApache. I see the issue with WordPress through my Sucuri Alerts reporting server addresses as reported ips, Joomla reporting server addresses as failed login ips while the apache logs report the correct addresses. Also in php testing, I see that the x-forwarded-for reports the server address if I use SSL but works normally if I don’t. Assuming that Hostgator has some kind of proxy, the x-forwarded-for should be an array of ips including the client and the proxies. So if they are terminating the SSL at the proxy and injecting the X-forward-for with the wrong information, it would explain what we are seeing. Now how to convince Hostgator the problem is on their end or above.
Here are some articles that shed some light:
https://en.wikipedia.org/wiki/X-Forwarded-For#Format
https://www.f5.com/company/blog/security-rule-zero-a-warning-about-x-forwarded-for
https://devcentral.f5.com/articles/using-quotx-forwarded-forquot-in-apache-or-phpForum: Plugins
In reply to: [WooCommerce] Same Ip Address for All OrdersI don’t know if this is directly related or not but here is an issue I am seeing on Hostgator. In Joomla, a security plugin started reporting everyone’s IP as the same. After some testing using just PHP, I found that if I connect with http then the remore_addr and the http_x_forwarded_for is the same and the client’s IP. If I connect with https, the remote_addr is the client’s IP and the http_x_forwarded_for is the web server. BTW all access logs report the correct ip addresses. Hope this helps. It seems related. Here is the code I used to test:
<?php
echo “REMOTE_ADDR= “;
echo $_SERVER[‘REMOTE_ADDR’];
echo “<br>”;
echo “HTTP_X_FORWARDED_FOR= “;
echo $_SERVER[‘HTTP_X_FORWARDED_FOR’];
echo “<br>”;
echo “HTTP_CLIENT_IP=”;
echo $_SERVER[‘HTTP_CLIENT_IP’];
?>Forum: Fixing WordPress
In reply to: My site disappearedMoons: You may have to clear your cache. Upgrade to PHP 7.1 and you should be able to reinstall the plugins without the error message coming back.
Forum: Fixing WordPress
In reply to: Parse and Fatal ErrorsIf you are running PHP 5.x, try upgrading to 7.1. I was getting this error and that fixed it.
Forum: Fixing WordPress
In reply to: My site disappearedCpanel is your web hosting control panel. It is not the same as your control panel for WordPress. If you are not sure how to get to it you might want to talk to your hosting company.
I had a website that was getting the same error message. I noticed that the site was still running PHP 5.4. I upgraded it to 7.1 and it works with no errors now. That may be a simple change in your Cpanel if the latest version of PHP is installed.
- This reply was modified 6 years, 3 months ago by fastrak.