A 105 Error is a DNS resolution error [1] and is one of the most commonly faced errors by a lot of users everyday who are using Webkit browsers like Safari or Google Chrome. It basically means that when you enter the URL of the website and hit enter, it tries to resolve the IP address of the website using a protocol called DNS (Domain Name System). If chrome is unable to reach the DNS server, the name resolution fails and you get the error 105.
This is a server issue that you have to address with your hosting provider.
If you are completely sure that keeping the plugin disabled fixes the problem, then please keep it that way until we can replicate the bug and release an update with the fix. However, I am confident that this is a server issue more than a problem with the plugin’s code.
[1] https://en.wikipedia.org/wiki/Talk%3AList_of_HTTP_status_codes#Error_105
Hello.
I’m absolutly sure about the browser/provider reason, because i asked for support from other people (and the hoster) and anyone faced the same 105 problem.
Disabling your plugin by FTP resolved the problem.
I’m using a rename wp-login page plugin, maybe this is the problem? (https://it.wordpress.org/plugins/rename-wp-login/)
A 105 Error is not an application-level error, it’s a server error.
The problem must be related to the use of a PHP built-in method used to reverse the hosting IP address, this is necessary to detect if your website is behind a firewall or not, and so in conjunction with a misconfiguration in your hosting account, the execution of that function is throwing the DNS resolution error.
Please keep the plugin disabled, I will fix the bug once I can reproduce it.
Ok, i disabled cloudflare and enabled again your plugin. now it works. then, there was a compatibility problem with cloudflare or a misconfiguration. do you have a guide for configurate correctly cloudflare for your plugin?
