FireMyst
Forum Replies Created
-
The lack of any kind of response speaks volumes. Time to stop using this plugin.
Forum: Fixing WordPress
In reply to: Am getting failed login attempts, but login page not hitThank you, but that page doesn’t help.
If you read the things I’ve tried, I’ve already been on that page and implemented some (“Deny Access to No Referrer Requests”) as detailed in my original post.
Be that as it may, it appears to be working again now… my servers were able to download the latest firewall rules files.
Tracert is also giving more feedback…
Tracing route to noc1.wordfence.com [69.46.36.28] over a maximum of 30 hops: 1 <1 ms <1 ms 2 ms m.home [192.168.1.1] 2 * * * Request timed out. 3 * * * Request timed out. 4 30 ms 19 ms 41 ms Bundle-Ether13.pie-edge901.perth.telstra.net [165.228.53.253] 5 120 ms 73 ms 37 ms bundle-ether6.pie-core1.perth.telstra.net [203.50.6.212] 6 57 ms 64 ms 53 ms bundle-ether3.way-core10.adelaide.telstra.net [203.50.6.234] 7 68 ms 134 ms 69 ms bundle-ether16.exi-core10.melbourne.telstra.net [203.50.6.231] 8 71 ms 76 ms 82 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124] 9 83 ms 260 ms 74 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93] 10 75 ms 86 ms 88 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98] 11 229 ms 236 ms 253 ms i-73.paix-core02.telstraglobal.net [202.84.247.45] 12 236 ms 225 ms 227 ms i-0-7-0-1.eqnx-core02.telstraglobal.net [202.84.143.209] 13 222 ms 220 ms 227 ms i-92.eqnx03.telstraglobal.net [202.84.247.17] 14 237 ms 221 ms 268 ms xe-4-3-1.mpr3.sjc7.us.zip.zayo.com [64.125.13.77] 15 243 ms 218 ms 274 ms ae19.mpr4.sjc7.us.zip.zayo.com [64.125.30.77] 16 239 ms 250 ms 231 ms ae16.cr2.sjc2.us.zip.zayo.com [64.125.31.14] 17 237 ms 243 ms 366 ms ae27.cs2.sjc2.us.eth.zayo.com [64.125.30.232] 18 251 ms 240 ms 248 ms ae3.cs2.sea1.us.eth.zayo.com [64.125.29.41] 19 247 ms 241 ms 271 ms ae1.mcs2.sea1.us.eth.zayo.com [64.125.29.23] 20 253 ms 242 ms 236 ms ae3.mpr1.sea26.us.zip.zayo.com [64.125.31.107]
Tracert from Australia:
Tracing route to noc1.wordfence.com [69.46.36.28] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms 192.168.43.1 2 * * * Request timed out. 3 24 ms 29 ms 26 ms 10.247.77.181 4 43 ms 24 ms 30 ms 10.246.243.253 5 27 ms 29 ms 17 ms 120.16.253.249 6 36 ms 38 ms 26 ms 220.101.68.53 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 75 ms 92 ms 84 ms 59.154.18.18 13 94 ms 92 ms 83 ms 59.154.18.8 14 81 ms 76 ms 87 ms syd-brdr-03.inet.qwest.net [63.146.27.141] 15 * * * Request timed out. 16 437 ms 249 ms 263 ms 63.149.178.150 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
It’s happening with me too.
My WordFence diagnostic page says the following:
“wp_remote_post() test to noc1.wordfence.com failed! Response was: cURL error 28: Connection timed out after 10001 milliseconds”When I run from any local computer (not the server my sites are hosted on) :
ping noc1.wordfence.com
Pinging noc1.wordfence.com [69.46.36.28] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.So it’s not a hosting provider issue.
My current IP that the ping is failing under is:
192.168.43.46
That’s in Australia.My sites are hosted in the USA, and it fails from there too.
Forum: Fixing WordPress
In reply to: v5.0.2 editor issues: puts in tags where it shouldn’tI did that. Thank you for the suggestion.
I’m hoping that if they are going to fix it, they do so before 2021.
Out of curiosity, do you know if it has the same issue with html
<pre>
tags?- This reply was modified 5 years, 10 months ago by FireMyst. Reason: Marked thread as resolved even though there's a follow up question
Forum: Fixing WordPress
In reply to: v5.0.2 editor issues: puts in tags where it shouldn’tThank you for the solution. I don’t know if that works for me yet, but briefly reading that’s just plain annoying.
Now all our pages have to be rewritten to include a custom code block whenever we don’t want html automatically inserted into our pages?
Grrr… that’s another 1-star rating for the editor. :-/
I can confirm it’s now fixed – working as expected on the 3 sites where I had the issue.
Great work and thank you!
Ok. Thank you. I will mark this topic as resolved trusting you’ll have the fix in the next update. Feel free to contact me if you need a tester for this. ??
As a reminder, the subdomain is hosted with an American hosting provider and according to https://www.iplocation.net/, the ip-address of the server is located in Clifton Park, New York.
So since the ip-address is in the white list, IP Geo Block shouldn’t be adding “,US” to the Whitelist Country Code should it?
Thank you for the response.
This doesn’t appear to work. I spoke to my hosting provider, and the A record for the server one of my subdomains is hosted on is 216.zzz.xxx.yyy (masked so not publicly shown here).
I added 216.zzz.xxx.yyy into the “Whitelist of extra IP addresses prior to country code ” configuration box and saved the changes.
I left IP Geo Block settings and then came back to confirm it had been saved in the list of IP address.
It was.
So I then disabled and re-enabled the plugin.
The whitelist Country Code went from “AU” -> “AU,US” again.
So either I’m doing something wrong, or it’s not working as expected.
???
I didn’t do anything, and it seems to have stopped occurring. Not sure unless it was trying to log something while in the middle of an update?
Forum: Plugins
In reply to: [IP Geo Block] error report on latest updateThanks @andrebraselmann.
Users shouldn’t have to do that though.
Hopefully the author will issue a fix to resolve it.
Forum: Plugins
In reply to: [IP Geo Block] Error on updating Versión 3.0.10I get the same error. Users shouldn’t have to uninstall and then reinstall the plugin. Otherwise, in the “details” when people click to see the latest version details it should be noted to uninstall first.
What’s the technical reason this can’t be resolved when the update installs itself?
Forum: Plugins
In reply to: [IP Geo Block] IP Geo block creating “origin errors”This looks like it was caused by some DNS settings not matching up on EZoic side of things.
So nice to see IP-Geo-Block was doing its job. ??