XF 2.0 Ongoing Login issues

mmirlach

Active member
Hi there,

I've installed Xenforo 2 for my community three days ago. From the very beginning, a number of users complained that they cannot login and would get the error message "Cookies are required to use this site. You must accept them to continue using the site." This would occur even after accepting the cookie notice on the bottom of the site

For me, the forum worked perfectly well for three days until I got the same error this evening. Even deleting cache / cookies in the browser and restarting the browser does not work. We're unable to reproduce the error as well, with community members reporting different browsers (Chrome, Firefox, IE).

Xenforo is sharing a database and server with a Wordpress installation as I plan to use Xpress to bridge a WP site with Xenforo.
This is the URL: https://www.gaming-universe.de/forum/

Is this a known issue / any clue on what I'm able to do to prevent this from happening?

Thanks,
Matt
 

Attachments

  • Screenshot_20181118-150629.webp
    Screenshot_20181118-150629.webp
    19.3 KB · Views: 12
Update: It's still behaving weirdly - after some time I was logged in again, without doing anything but refreshing the site. Users are reporting the same.
Does anyone have an idea what's causing this? It's becoming a huge issue for me
 
Update 2: I might have found the issue. My server is using SSL but Xenforo seems to omit the https - which again seems to cause problems. When I manually enter the URL with https instead of http, login always seems to work. With http I do get the cookie error.
Could this be the case and can anyone advise if this guide still applies to XF 2.0 (or point me to the right direction): https://xenforo.com/community/resources/how-to-implement-ssl-to-secure-http-traffic-https.5425/
 
Yeah, I just compared the htaccess from XF1.5 and 2.0 and noticed that there are no real differences so I added the commands to force HTTPS to the htaccess. I already had the https URL set in the Xenforo admin options but many members were still browsing with http - so I assume this might have caused issues. Let's see if this is ironed out now.
 
Back
Top Bottom