• Resolved franksysgfx

    (@franksysgfx)


    Our troubleshooter was not able to access your sitemap for testing. Your server’s security software might be blocking requests sent by the troubleshooter. If this is the case, whitelisting your server’s IP might resolve the issue.

    How do I solve this problem? It is not clear, there is no demonstration video or more information

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Dmytro – WPMU DEV Support

    (@wpmudevsupport16)

    Hello @franksysgfx,

    I hope you’re doing well today!

    In case the sitemap troubleshooter can’t access the sitemap, you may need to whitelist SmartCrawl IP addresses, if you have a security plugin like Wordfence, or in hosting firewall (verify this with the hosting support).

    Please refer to the following guide on whitelisting WPMU DEV IPs:

    https://wpmudev.com/docs/getting-started/wpmu-dev-ip-addresses/

    Hope this helps. Let us know if you need any further assistance!

    Best Regards,
    Dmytro

    Thread Starter franksysgfx

    (@franksysgfx)

    For some reason, despite deactivating the plugin and checking Cloudflare I still have the problem, I want to ask what the repercussions are of not putting the IPs in the white list, what could go wrong with this plugin?

    Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @franksysgfx

    I re-read this ticket and it seems my colleague slightly missed the point.

    The error that you are getting doesn’t suggest allowing our IPs but it specifically says “If this is the case, whitelisting your server’s IP might resolve the issue.

    There is no implications for the site in terms of SEO/search engine indexing if you don’t allow our IPs. The troubleshooter feature works within your site and this error means that, basically, plugin on your site was not able to successfully connect to your site.

    That usually still points to some sort of security configuration issues but may also be related to some server misconfiguration.

    If you go to “Tools -> Site Health” page in your site’s back-end, do you see any warnings there related to SSL and/or loopback and/or cURL? If yes, what exactly these warnings are saying?

    Also, despite troubleshooter error, are you able to actually visit and open sitemap URL of your site in browser – or are you getting some errors in browser too when you access it directly?

    Kind regards,
    Adam

    Thread Starter franksysgfx

    (@franksysgfx)

    I was able to solve it, the malcare plugin (antivirus that does not affect the performance of wordpress) had not been installed correctly, I sent a ticket to them because when I deactivated it it worked wonderfully and that is why when I included your IP in cloudflare it did not It worked, now everything is going great in my wordpress multisite, just one additional question, When I save a configuration for all the sub-sites, and uncheck all the Modules options, will the configuration remain the same? Will the sub-sites maintain the configuration despite having disabled the modules as I show in the photo? https://ibb.co/XXGXZ8J

    Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @franksysgfx

    Thank you for response and I’m glad to know it’s solved now!

    As for your question:

    Those settings for modules there are about “access” so they determine what parts of the plugin can be configured directly via the sub-site.

    The “config” is not about the modules “access” but actual SEO configuration to be “pre-applied” (like e.g. “Titles & Meta” configuration etc). If you have modules disabled – it won’t be possible to change such configuration directly on subsite that got such configuration pre-applied.

    Note also: saving that configuration doesn’t mean it’s applied automatically to all sub-sites at the same time; instead it’s only applied to sub-sites created after such config is saved.

    Best regards,
    Adam

    Plugin Support Zafer – WPMU DEV Support

    (@wpmudevsupport15)

    Hi @franksysgfx,

    We are marking this topic as resolved since the issue has been fixed. Please let us know in case you need further help.

    Kind regards,
    Zafer

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Troubleshoot Sitemap’ is closed to new replies.