v1.4.14 - Bad Request when saving Tab options #141

New issue

Closed

opened 2026-02-20 10:24:27 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 10:24:27 -05:00

Owner

Originally created by @JNR8 on GitHub (Sep 17, 2018).

After upgrading to v1.4.14 I get the following error when saving Tab options:

400 Bad Request
The plain HTTP request was sent to HTTPS port

I took a look at the HTML presented to the browser and it seems that there is a specific http://**** url specified instead of a relative URL which is breaking the submit button for me when offloading SSL on an NGINX reverse proxy.

Could you please take a look at amending this in your next release?

Thank you.

Originally created by @JNR8 on GitHub (Sep 17, 2018). After upgrading to v1.4.14 I get the following error when saving Tab options: 400 Bad Request The plain HTTP request was sent to HTTPS port I took a look at the HTML presented to the browser and it seems that there is a specific http://**** url specified instead of a relative URL which is breaking the submit button for me when offloading SSL on an NGINX reverse proxy. Could you please take a look at amending this in your next release? Thank you.

deekerman closed this issue

2026-02-20 10:24:28 -05:00

deekerman commented

2026-02-20 10:24:29 -05:00

Author

Owner

@aptalca commented on GitHub (Sep 17, 2018):

Is your proxy pass directive pointing to an http or https address?

@aptalca commented on GitHub (Sep 17, 2018): Is your proxy pass directive pointing to an http or https address?

deekerman commented

2026-02-20 10:24:29 -05:00

Author

Owner

@JNR8 commented on GitHub (Sep 17, 2018):

The proxypass is set to http://ipaddress:portnumber

I do have the setting pages restricted with an ID and password. but this happens when I turn that off also.

@JNR8 commented on GitHub (Sep 17, 2018): The proxypass is set to http://ipaddress:portnumber I do have the setting pages restricted with an ID and password. but this happens when I turn that off also.

deekerman commented

2026-02-20 10:24:29 -05:00

Author

Owner

@aptalca commented on GitHub (Sep 17, 2018):

Change that to https and use the https port. It's in the readme.

@aptalca commented on GitHub (Sep 17, 2018): Change that to https and use the https port. It's in the readme.

deekerman commented

2026-02-20 10:24:29 -05:00

Author

Owner

@JNR8 commented on GitHub (Sep 18, 2018):

Whilst this did fix the issue, it was not the only issue that was contributing to this behavior. It seems that, somehow, during the creation of new containers within Docker MAC addresses on the Bridge network were duplicated. This was causing my slow down issues as well as issues I had with other containers. Once i gave them unique MAC addresses everything started to work nicely.

Thanks for your help.

@JNR8 commented on GitHub (Sep 18, 2018): Whilst this did fix the issue, it was not the only issue that was contributing to this behavior. It seems that, somehow, during the creation of new containers within Docker MAC addresses on the Bridge network were duplicated. This was causing my slow down issues as well as issues I had with other containers. Once i gave them unique MAC addresses everything started to work nicely. Thanks for your help.