• Resolved rsmithgs

    (@rsmithgs)


    Hello, today I went into Wordfence Central and it stated that I had connection issues with 3 of my sites.
    The exact error was: Failed to connect to [domain] port 443: Connection refused

    I have attempted following all of the instructions on similar tickets like this one: Unable to resolve domain redirects

    The steps there did not work. I’ve also attempted with my Hosting company to whitelist Wordfences’ IPs as listed here Wordfence IPs and update the .htaccess file to see if that would help.

    I’ve also checked that the SSLs were correct and my WP_HOME and WP_SITEURL are matching with the secure domain link.

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Support WFAdam

    (@wfadam)

    Hello @rsmithgs and thanks for reaching out to us!

    Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Once I get your diagnostic I will run an SSL test and check other things that might be causing the issue.

    Thanks again!

    Thread Starter rsmithgs

    (@rsmithgs)

    I have sent a diagnostic report.

    Thank you for your assistance!

    Plugin Support WFAdam

    (@wfadam)

    Thanks for sending that!

    I checked your SSL, which looks to be ok. I also checked your REST API access which is working.

    I am thinking something is possibly blocking our Wordfence Central servers. Make sure any CDN’s/Proxies/Host you might be using arent blocking requests from:
    Wordfence Scan Servers:

    44.239.130.172
    44.238.191.15
    35.155.126.231

    Wordfence Central Servers:

    54.68.32.247
    44.235.211.232
    54.71.203.174

    Once you have checked this, try to reconnect and let me know what you find!

    Thanks again!

    Thread Starter rsmithgs

    (@rsmithgs)

    Hello,

    I had recently whitelisted each of those IPs except 44.235.211.232, I have just added that IP address, but I am still unable to readd my site. The error is still “Unable to resolve domain redirects”

    Plugin Support WFAdam

    (@wfadam)

    Now that you have that on the Allowlist, try these steps:

    Head over to Wordfence Central, go to the Connection Issues tab. Clear out any sites that might be in here.

    Now head over to your site and log in as an admin. Navigate to Tools > Diagnostics > Other Tests > Clear all Wordfence Central connection data. Clear the connection data and then from the Wordfence Dashboard, click on “Connect this site” in the Wordfence Central widget.

    Let me know how it goes!

    Thanks again!

    Thread Starter rsmithgs

    (@rsmithgs)

    I have followed the instructions again, but no luck.

    Plugin Support WFAdam

    (@wfadam)

    Ahh I see you sent in three diagnostics for three sites!

    Test my suggestions with thinkingxxxxxxxxx.org.

    I tested stanxxxxxx.org as well and it seems to be good.

    I did an SSL scan on collxxxxxx.org and it looks to have some bad results. You might want to check with your SSL provider for that site.

    https://www.ssllabs.com/ is a good site to test SSL.

    Let me know how the test goes on those other 2 sites!

    Thanks again!

    Thread Starter rsmithgs

    (@rsmithgs)

    I had previously tested with stanxxxxxx.org and it still gave the unable to resolve domain redirects issue. I just tested again with thinkingxxxxxxxxx.org but it is showing the same issue. I will look through https://www.ssllabs.com/ for issues related to collxxxxxx.org, but all 3 of my websites were provided SSLs through the same source.

    Thread Starter rsmithgs

    (@rsmithgs)

    I see your previous test at ssllabs.com and it seems that it was successful with the IPv4 address, but IPv6 experienced an unexpected failure.

    Plugin Support WFAdam

    (@wfadam)

    In my experience, when the error is mentioning redirects, it’s usually the SSL that is causing the issue. Reach out to your SSL provider and pose the question to them.

    Let me know what they say!

    Thanks again!

    Thread Starter rsmithgs

    (@rsmithgs)

    My website host found an AAAA record related to the domain with the issue and has removed and purged the cache. I will try again in an hour.

    Plugin Support WFAdam

    (@wfadam)

    Sounds good!

    Make sure to Clear Data Connection and I mentioned before, before you try to connect it again.

    Let me know how it goes!

    Thanks again!

    Thread Starter rsmithgs

    (@rsmithgs)

    I have tried again, but no luck. I’m assuming this is because the AAAA record hasn’t been purged from everywhere yet. I will try again when I see all AAAA records purged at https://dnschecker.org/#AAAA

    Thread Starter rsmithgs

    (@rsmithgs)

    Unfortunately, it doesn’t seem like removing the AAAA records helped.
    When I go to Tools > Diagnostics > Other Tests > Clear all Wordfence Central connection data and then go back to Dashboard I am still seeing “Wordfence Central Status” “Disconnected by on June 26, 2021” “Reconnect This Site” “Visit Wordfence Central”

    If I Clear all Wordfence Central connection data why is this still recognizing that it was once connected? Perhaps it is not truly deleting all connection data?

    Thread Starter rsmithgs

    (@rsmithgs)

    Hello @wfadam, unfortunately, it doesn’t look like removing the AAAA record helped. I just attempted to reconnect to Central again after going to Tools > Diagnostics > clear data connection and it still says “Unable to resolve domain redirects”.
    I have no known redirects and that can be confirmed here: https://httpstatus.io/

    Any other suggestions would be greatly appreciated!

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Unable to resolve domain redirects’ is closed to new replies.