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

Reverse proxy setup "HTTP Web root" not saving. #7835

Closed
cino opened this issue Mar 11, 2020 · 1 comment · Fixed by #7841
Closed

Reverse proxy setup "HTTP Web root" not saving. #7835

cino opened this issue Mar 11, 2020 · 1 comment · Fixed by #7841
Labels
triage Untriaged issue

Comments

@cino
Copy link

cino commented Mar 11, 2020

Describe the bug
I'm trying to set up a reverse proxy towards Medusa (domain, path based), which sort of works fine on the proxy end but I can't seem to save the setting called "HTTP Web root". Tried multiple times to enter this field and save it and however it gives a successful message, when I reload the page the input field is empty.

Reason I think I need this field is if I try to access the Medusa interace over my reverse proxy, lets say: example.com/medusa it redirects towards example.com/login/?next=%2Fmedusa . This should redirect towards example.com/medusa/login/

To Reproduce
Steps to reproduce the behavior:

  1. Go to General Configuration
  2. Click on Interface
  3. Scroll down to HTTP Web root
  4. Fill the field
  5. Save.
  6. Reload
  7. Tada, empty field

Expected behavior
I expect this field to be stored successfully, which would than solve my issue with my reverse proxy.

Screenshots

image

Medusa (please complete the following information):

  • OS: Linux-3.10.105-armv7l-with-glibc2.4 // DSM 6.2.2-24922 Update 4
  • Branch: master
  • Commit: ee1b898
  • Python version: 2.7.14
  • Database version: 44.14

Additional context

I don't have any logs for this, turned on debug logging but couldn't get the interface to show me the debug logs. If there is another location I can find these (via ssh/command line) I'd be glad to try.

Thanks in advance.

@triage-new-issues triage-new-issues bot added the triage Untriaged issue label Mar 11, 2020
@medariox
Copy link
Contributor

Thanks for the bug report. Will be fixed with #7841

@medariox medariox linked a pull request Mar 14, 2020 that will close this issue
3 tasks
medariox added a commit that referenced this issue Mar 15, 2020
* Catch indexer specific exceptions in show refresh

* Fix saving of web_root

* Fix test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Untriaged issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants