Unpublished pages point to admin login instead of showing 404 page

[uiui]

Hello,

I have no idea why unpublished pages lead to the admin login instead of displaying the error 404 page.

Does anyone have an idea where I should look at?

[uiui]

Now I even have a case in which the login form shows up even though I moved the page to the trash. I also can't use a jumplink to redirect to a different URL.

[uiui]

Am I the only who ran into this issue?

I might add that jumplinks are working for other languages as long as the page is still published, and I deactivate those languages. As soon as I unpublish the whole page, users are again ending up on the admin login.

[wbmnfktr]

Which version of ProcessWire are you using?
Which modules do you use?

Is the 404 page working at all?
Does the template exist?
Is there a redirect defined in the template?
Is it the original 404 page, with ID 27?

Is there something special with this setup?
URL segments?
Any hooks?
Multisite?
Multilanguage (I guess)?

 

[uiui]

36 minutes ago, wbmnfktr said:

Which version of ProcessWire are you using?
Which modules do you use?

Is the 404 page working at all?
Does the template exist?
Is there a redirect defined in the template?
Is it the original 404 page, with ID 27?

Is there something special with this setup?
URL segments?
Any hooks?
Multisite?
Multilanguage (I guess)?

 

Thank you for your response

1. Processwire 3.0.210
2. Duplicator
   FieldtypeColor
   FieldtypeFontIconPicker
   FieldtypeRepeaterMatrix
   FileValidatorSvgSanitizer
   FormBuilder
   GoogleClientAPI
   ImageExtra
   InputfieldColor
   InputfieldFontIconPicker
   MarkupFontIconPicker
   MarkupSimpleNavigation
   PageimageSource
   PageSnapshot
   PasswordForceChange
   ProCache
   ProcessAdminActions
   ProcessDuplicator
   ProcessExportProfile
   ProcessJumplinks
   ProcessLanguageFieldExportImport
   ProcessProCache
   ProcessVersionControl
   ProcessWire dev
   ProcessWire master
   ProcessWireUpgrade
   RestApi
   Sassify
   SeoMaestro
   SimpleContactForm
   TextformatterHannaCode
   TextformatterVideoEmbed
   VersionControl
3. Yes, with a random URL that isn't linked to any page, it works (or using the URL of a deactivated language)
4. The 404 template exists
5. No redirects in the 404 template
6. Yes, 27
7. No URL segments
8. No hooks
9. One site
10. Multi-language

I can't of anything fancy to the configuration that might cause that issue.

[wbmnfktr]

1. RestApi
2. Jumplinks

These are the only modules that take care of or interfere with your URLs - at least I know this for sure with these two.

What I would do now is this:

• Check the Access settings in the template
• Check the 404 monitor in Jumplinks to see if the 404 exception actually exists/gets caught.
• Check for existing jumplinks in Jumplinks for that URL.
• Check that specific page you are testing with for entries in the settings tab under What other URLs redirect to this page?
  • Check if PagePageHistory module is installed, which is needed for the previous point
• Check redirects in .htaccess.
• Check if the RestApi module is involved here and double check that setup.
• Check the settings in the Languages Support - Page Names module
• Check if there is something in _init.php, init.php, ready.php and maybe even config.php.
  • Or search any of your templates for: $session->redirect and redirect

Redirects don't happen that random that's why I am bit confused for this one.

[uiui]

I've looked at all those things and compared my local installation, on which it works, with the productive one and didn't see any differences.

What I find interesting is that the 404 monitor also doesn't include the request, only after I change the page's URL.

[wbmnfktr]

Just another guess... what kind of setup is that production one?
Standard Apache or maybe NGINX or CDN in-between there somewhere?