Logged in but still getting http_auth

#1

So after moving the hosts… it seems I now have double authentication for protected content files…

After logging in as a user, if I click on the content that is protected by s2member, in this case audio file for download/stream locally hosted, I get the remote authorization window.
This did not happen before.

What should I check to figure out what needs to be updated to remove this second layer of login?

Ideally once logged in you should not get the second authorization.

Thanks in advance.

#2

What precisely do you mean by that? How is this requirement manifesting itself?

#3

I can click on protected content and taken to the subscribe page - normal

I log in and then when i click on the podcast I get the authorization box - not normal

Also once I am logged in via the remote auth box, it persists, after I am logged out of the site, I can still stream the content.

There may be a few things happening here I use powerpress plugin and host the files on my server.

Seems like two functions how do I make the login one function.

#4

Are you talking about an authorization box from the server? If so, this is a server configuration issue.

#5

Thanks, I found a few things on the .htacess file that might have been blocking for a server level authentication. That was not present on the old configuration - .well-known for let’s encrypt which I am not using on this site. Maybe that was it?

I also disabled a few plugins I thought might be interfering like wp super cache and made the alternates views protected in s2member.

I still have issues with accessing the feed/podcast on mobile devices with the remote auth. It shows up but on mobile it is not asking for the auth. It works in i-tunes on the desktop, it is just mobile. Any work arounds for protected content on mobile? I tried the url in the apps as http://username:password@mysite.com/feed/podcast/ that didn’t seem to work.

thanks for reading

#6

Siouxsie,

You really need to deactivate all the other plugins on your site and test how things work then. If you still have a problem, it means either you haven’t completely followed the s2Member instructions or there is an issue with a server setting or your .htaccess file.

Once you have that all working properly, you can then reactivate your plugins one by one, and test each time to make sure that the problem doesn’t recur. If it does, you have a conflict with that plugin.

So far as caching is concerned, I’d strongly recommend using Comet Cache as it’s by the s2Member developers, and the two plugins are designed to work together.

1 Like