Simple Machines Community Forum

SMF Support => SMF 2.1.x Support => Topic started by: dsanchez on May 05, 2019, 12:15:42 PM

Title: Unable to verify referring URL. Please go back and try again.
Post by: dsanchez on May 05, 2019, 12:15:42 PM
Several of these errors in my log:

Type of error: User
Unable to verify referring URL. Please go back and try again.
http://curefans.com/index.php?action=login2


anyone getting similar messages?
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: dsanchez on May 05, 2019, 12:46:53 PM
Ok, this seems a bigger issue than I thought as some members are reporting they can not login :'(
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: albertlast on May 06, 2019, 12:18:15 AM
Why you use login2?
The right url would be http://curefans.com/index.php?action=login and
this work fine on your side.
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: Arantor on May 06, 2019, 03:38:38 AM
Quote from: albertlast on May 06, 2019, 12:18:15 AM
Why you use login2?
The right url would be http://curefans.com/index.php?action=login and
this work fine on your side.

Probably because it's failing on the actual "user has entered a password" step (login is the form, login2 is the handler)

I did go to the site and see that the login pop up also doesn't work properly :( just returns "error".
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: dsanchez on May 06, 2019, 05:20:58 AM
Why is this happening? I don't have the problem but it seems some of the users have this problem :(
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: dsanchez on May 06, 2019, 05:26:15 AM
could you guys advise on disable the login popup and instead just redirecting the login link to http://curefans.com/index.php?action=login ?
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: Arantor on May 06, 2019, 05:40:33 AM
Only way to remove it is to remove the reqOverlayDiv call on it, there's no option for it. But would be better to fix the error...
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: SychO on May 06, 2019, 05:55:48 AM
try forcing www. from your htaccess
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: Arantor on May 06, 2019, 05:59:28 AM
Or setting subdomain independent cookies - the issue looks to be caused by session mismatch between www. and non-www. use.
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: SychO on May 06, 2019, 06:03:55 AM
Quote from: Arantor on May 06, 2019, 05:59:28 AM
Or setting subdomain independent cookies - the issue looks to be caused by session mismatch between www. and non-www. use.

indeed

@dsanchez Maintenance > Cookies and session > Use subdomain independent cookies
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: dsanchez on May 06, 2019, 06:12:25 AM
Quote from: SychO on May 06, 2019, 06:03:55 AM
Quote from: Arantor on May 06, 2019, 05:59:28 AM
Or setting subdomain independent cookies - the issue looks to be caused by session mismatch between www. and non-www. use.
indeed
@dsanchez Maintenance > Cookies and session > Use subdomain independent cookies

can't see that option (see attachment)

Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: SychO on May 06, 2019, 06:38:10 AM
that's because you have to disable local storage of cookies, but you clearly can't even edit those settings, you need to fix that
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: Arantor on May 06, 2019, 06:43:28 AM
And the clue is the big "Settings.php is readonly" message up top...
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: dsanchez on May 06, 2019, 02:21:34 PM
done! let's see if this solves the issue...
Title: Re: Unable to verify referring URL. Please go back and try again.
Post by: dsanchez on May 07, 2019, 02:49:41 PM
Issue seems solved after implemented the suggested changes :)