Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Ability to add apache http auth #12

Closed
deedeefink opened this issue Oct 25, 2018 · 8 comments
Closed

[Request] Ability to add apache http auth #12

deedeefink opened this issue Oct 25, 2018 · 8 comments
Assignees
Labels
enhancement New feature or request

Comments

@deedeefink
Copy link

Thanks for v2.

I would like the option to add Apache http auth to the domains as an extra layer of security. I would imagine that adding one auth for all the domains as part of the environment section would be the easiest.

However, I have a use-case where I would like to give access to ie. Ombi, but not the other URLs, therefore it would be good to either have an option to set the password per domain, or to enable/disable the auth per domain. This way I can either controll access with different passwords or i can disable authentication on OMBI.

Thanks

@deedeefink deedeefink changed the title Ability to add apache http auth [Request] Ability to add apache http auth Oct 25, 2018
@TechPerplexed TechPerplexed self-assigned this Oct 25, 2018
@TechPerplexed TechPerplexed added the enhancement New feature or request label Oct 25, 2018
@TechPerplexed
Copy link
Owner

Thanks for the suggestion! In fact the base for this is already in place, it's just a matter of implementing this - stay tuned!

@TechPerplexed
Copy link
Owner

And... it's added. Go try it 😄

@deedeefink
Copy link
Author

deedeefink commented Oct 27, 2018

Tried, but not working :-(

I added a user to Sonarr, but no http auth is popping up when I access the URL. I tried a private session, also a different browser, I cleared my cache and I restarted the server. No auth window.

sonarr

@deedeefink
Copy link
Author

I also tested a freshly installed server but still no luck.

  1. I installed Sonarr as the only app

  2. Right after installing Sonarr I selected Secured server and got the following error:
    sonarr

  3. Second time I secured the server I got no errors, but the auth does not work.

@TechPerplexed
Copy link
Owner

Ahhhh.... Weird... it worked when I tested at first... Let me look into that!

@TechPerplexed
Copy link
Owner

Hmm yes definitely working correctly here... can you try this just to be sure:

  1. Update Gooby to the latest version (option E - A in the menu)
  2. Run a system cleanup (option E - C in the menu)
  3. Wait till it's done... then try again...

Let me know if that sorted it!

@deedeefink
Copy link
Author

Your steps worked, which is good but also strange.
Today I reinstalled my servers 3-4 times today Linux+Gooby and tested the hell out of it. I always used the sudo wget http://bit.ly/GetGooby -O /tmp/install.sh && sudo bash /tmp/install.sh to install.

I did not perform any update Gooby or System cleanup since his was a fresh server install and Gooby install. Therefore it's strange that this worked only after update (despite no new release) and system cleanup on a fresh install.

But hey, it works.
Now I just need to figure out how Sonarr will talk to Jackett and the custom Torznab behind http auth :-)

@TechPerplexed
Copy link
Owner

There is one thing I can think of... you might have installed it right before I noticed that the "s" in "Security" wasn't capitalized. Check if you have two folders in /var/local/Gooby, 1 named security and 1 named Security. If so, you can remove the one named "security".

If that's not it, I blame it in Gremlins 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants