Redirects to blank page

  • slippers

    (@slippers)


    1 week, 6 days ago

    Hi, love the plugin. But it stopped redirecting to one of my main affiliate partners.

    The URL: https://systeme.io

    Any idea why this is?

    Other URL’s work flawless.

    • This topic was modified 1 week, 6 days ago by slippers.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support oiler

    (@eulerarthur)

    1 week, 5 days ago

    Hi there,

    I checked your link and can confirm what you’re seeing. When someone opens https://blogwinst.nl/go/systeme/, the server sends a redirect response but without a destination URL, so the browser ends up on a blank page instead of systeme.io. Your other links on the same site seem to redirect normally, so this looks tied to the systeme link itself rather than a general plugin or site issue.

    The most common cause is something off in the destination URL on that one link – often a missing https://, a bad copy-paste with hidden characters, or a broken override if you’re using geolocation or link scheduling in Pro. For systeme.io, the destination should look like https://systeme.io/?sa=YOUR_AFFILIATE_ID.

    Could you please open that link in ThirstyAffiliates, delete the destination URL, type it in again by hand, save, clear any site cache you’re using, and test /go/systeme/ in a private window? If it still misbehaves, a screenshot of the destination URL field (you can redact part of the affiliate ID) would help, along with whether geolocation or scheduling is enabled on that link.

    Thanks,
    Euler.

    Thread Starter slippers

    (@slippers)

    1 week, 4 days ago

    Thank you Euler. I changed the link by typing it by hand and leaving out the affiliate code. Saved, cleared cache and opened in private window. Just to see if it works on the root domain, but no luck.

    Screenshot : https://imgur.com/a/cqQ6qMq

    Please test on your end if you can get it to work on one of your sites, to see if you can reproduce this?

    Plugin Support oiler

    (@eulerarthur)

    1 week, 3 days ago

    Hey there,

    Thanks for sticking with this. I retested and I can confirm it’s not ThirstyAffiliates itself – a fresh systeme.io link redirects fine on my own site (https://euler.apps.cspf.co/oilerart/system/), and on yours every other affiliate link seem to work while only the systeme one comes back blank. The redirect response is actually being sent, but the part that tells the browser where to go is getting stripped out somewhere on your end, which usually points to a plugin, theme, or server interaction rather than the link itself.

    A couple of quick things worth trying first: ensure to have a full backup, then head to Settings -> Permalinks, click Save (no changes needed) to flush the rewrite rules, and test again. If that doesn’t do it, edit the systeme link and temporarily point it at something neutral like https://example.com, save, clear cache, and open the link – if that redirects fine, we know the link is healthy and the issue is specific to the systeme.io destination being filtered.

    If it’s still blank, let’s rule out a conflict. Once again, with a full backup in place (ideally on a staging copy, not the live site), deactivate any plugins not related to ThirstyAffiliates and switch to a default theme like Twenty Twenty-One. If the redirect starts working, reactivate things one by one until it breaks again so we can spot the culprit.

    It’d also really help to see what’s happening under the hood. Could you please enable debug logging by adding this to your wp-config.php:

    // Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

// Use dev versions of core JS and CSS files
define( 'SCRIPT_DEBUG', true );

    More on this here if you’d like to read up: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/.

    Once that’s in, reload the systeme link to reproduce the issue, then check for a debug.log file inside wp-content and paste the last few lines back here. Between the conflict test and the log, we should be able to pin down exactly what’s eating that redirect.

    Looking forward to your reply. Thanks!

    All the best,
    Euler.

    Thread Starter slippers

    (@slippers)

    1 week, 3 days ago

    Hi Euler, thanks for the follow up.

    1. Permalinks, click Save (no changes needed) to flush the rewrite rules, and test again. No joy.
    2. Temporarily point it at something neutral. This works and it redirects fine to other domains.
    3. Deactivate any plugins not related to ThirstyAffiliates and switch to a default theme like Twenty Twenty-One. All plugins deactivated except TA and base WP theme selected did not work.

    Here’s the requested debug file:

    [03-Jun-2026 06:28:36 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>rocket</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-includes/functions.php on line 6170
    [03-Jun-2026 06:28:36 UTC] PHP Deprecated:  Creation of dynamic property WP_Rocket\Engine\Preload\SitemapPreloadSubscriber::$options is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/Engine/Preload/SitemapPreloadSubscriber.php on line 26
    [03-Jun-2026 06:28:36 UTC] PHP Deprecated:  Creation of dynamic property WP_Rocket\Engine\Preload\SitemapPreloadSubscriber::$sitemap_preload is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/Engine/Preload/SitemapPreloadSubscriber.php on line 27
    [03-Jun-2026 06:28:36 UTC] PHP Deprecated:  Automatic conversion of false to array is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/3rd-party/plugins/seo/yoast-seo.php on line 10
    [03-Jun-2026 06:28:37 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>rocket</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-includes/functions.php on line 6170
    [03-Jun-2026 06:28:37 UTC] PHP Deprecated:  Creation of dynamic property WP_Rocket\Engine\Preload\SitemapPreloadSubscriber::$options is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/Engine/Preload/SitemapPreloadSubscriber.php on line 26
    [03-Jun-2026 06:28:37 UTC] PHP Deprecated:  Creation of dynamic property WP_Rocket\Engine\Preload\SitemapPreloadSubscriber::$sitemap_preload is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/Engine/Preload/SitemapPreloadSubscriber.php on line 27
    [03-Jun-2026 06:28:37 UTC] PHP Deprecated:  Automatic conversion of false to array is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/3rd-party/plugins/seo/yoast-seo.php on line 10
    [03-Jun-2026 06:28:42 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>rocket</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-includes/functions.php on line 6170
    [03-Jun-2026 06:28:42 UTC] PHP Deprecated:  Creation of dynamic property WP_Rocket\Engine\Preload\SitemapPreloadSubscriber::$options is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/Engine/Preload/SitemapPreloadSubscriber.php on line 26
    [03-Jun-2026 06:28:42 UTC] PHP Deprecated:  Creation of dynamic property WP_Rocket\Engine\Preload\SitemapPreloadSubscriber::$sitemap_preload is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/Engine/Preload/SitemapPreloadSubscriber.php on line 27
    [03-Jun-2026 06:28:42 UTC] PHP Deprecated:  Automatic conversion of false to array is deprecated in /var/www/vhosts/funnelfood.com/blogwinst.nl/wp-content/plugins/wp-rocket/inc/3rd-party/plugins/seo/yoast-seo.php on line 10
    Plugin Support oiler

    (@eulerarthur)

    1 week, 2 days ago

    Hey there,

    Thanks for all the info and for your patience.

    Looking at the debug log, WP Rocket is still running during the test, which makes sense – deactivating it from the WordPress admin doesn’t fully remove it because it writes rules directly into your server’s .htaccess file, and those stick around regardless. So the conflict test wasn’t quite clean, but honestly I don’t think WP Rocket is the real culprit here anyway.

    The bigger clue is that swapping the destination to another domain works fine. That tells us ThirstyAffiliates and the link itself are healthy – the issue is specifically with systeme.io as a destination. Your server seems to run LiteSpeed, which has its own built-in firewall and security layer that operates completely independently from WordPress and its plugins. Systeme.io does end up on some server-level block lists because it’s widely used in spam and phishing setups, so it’s not uncommon for hosts to filter it.

    At this point I’d recommend reaching out to your hosting provider and asking them to check whether outbound redirects to systeme.io are being blocked at the server or firewall level. You can use something like this:

    “Hi, I’m having an issue where a redirect on my site (blogwinst.nl) to https://systeme.io is not working – the server returns a 302 response but without a Location header, so visitors end up on a blank page. Redirects to other domains work fine. I’ve ruled out WordPress plugins and themes as the cause. Could you check whether systeme.io is being blocked or filtered at the server/firewall/WAF level, and whitelist it if so? Thank you.”

    Once they confirm or clear that, please let us know what they say.

    Thanks,
    Euler.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.