Back to Blog
Ftp inetinfo exe6/7/2023 ![]() ![]() This scenario is another example why I recommend immediately checking server logs, any time there's a problem with FTP publishing. If you see an IP address owned by Google being filtered, update your filter. If you see an entry mentioning rejection by IP address, when you're trying to publish your blog, verify the address using WhoIS. If you are having problems with blog publishing by FTP from Blogger, check your firewall logs. It's good that Blogger is willing to provide a list of IP addresses used in the FTP process, but I would never bet on the list being 100% up to date. That's a Blogger computer, but is it the only one? We'll only find out if more bloggers report finding other addresses being rejected. Let's check out "72.14.206.132", using the All-NetTools WhoIs utility. We updated our firewall rules with this new IP (72.14.206.132) and publishing started to work. ![]() We were able to see requests from a new google IP (72.14.206.132) address being dropped by our firewall. It's not clear whether those 2 addresses completely replace the previously defined addresses:ĭuring the past couple weeks, several bloggers have found that list to be inaccurate. A list of IP addresses is provided in Blogger Help: Can I use Blogger if my server is restricted by IP address or behind a firewall?. If you're publishing your Blogger blog by FTP to a remote host server, and the host server protects itself by an IP filter, the filter has to allow access to any computers used by Blogger for FTP transfer. As long as your clients publish from computers with known IP addresses, and those computers are never used by people with malicious intent, this is a good strategy. One of the easiest ways to protect the server is to deny update access to computers with unknown IP addresses. If you have a server that is used to host web sites, you need to protect the server, and the web sites, from malicious access.
0 Comments
Read More
Leave a Reply. |