mirror of
https://github.com/SignTools/SignTools.git
synced 2026-04-26 10:25:54 +03:00
[GH-ISSUE #410] OTA Manifest error when on https #102
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SignTools#102
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @8mbe on GitHub (Mar 21, 2024).
Original GitHub issue: https://github.com/SignTools/SignTools/issues/410
I tried basic troubleshooting first
Describe the bug
When trying to install an app from the signtools (hosted locally and exposed through reverse proxy Nginx Proxy Manager) I get
using OTA manifest proxy, installation may not work. The url that I access my instance of signtools ishttps://sign.xxx.com(where xxx is my domain name), but it reports that it setsbase_urltohttp://sign.xxx.com(WRN using OTA manifest proxy, installation may not work base_url=http://sign.xxx.com)To reproduce
Steps to reproduce the behavior:
Expected behavior
A
Do you want to install this app?prompt appears and app installsLogs
sign.xxx.comand ips are replaced withxxx.xxx.xxx.xxxfor my own safety_signtools_logs.txt
Screenshots
None.
System configuration
signtools/signtools)@ViRb3 commented on GitHub (Mar 21, 2024):
You need to pass the
X-Forwarded-Proto: httpsheader from your reverse proxy to SignTools, see https://github.com/SignTools/SignTools/blob/master/INSTALL.md#4a-reverse-proxy.@8mbe commented on GitHub (Mar 21, 2024):
It is already done by NPM (Nginx Proxy Manager), so it doesn't seem to be the problem. Any other solution?
@ViRb3 commented on GitHub (Mar 21, 2024):
I can think of a few potential issues:
$schemeis not https; maybe try hardcodinghttpsinstead of$schemejust to test?proxy.conf? maybe it's overriding something?@8mbe commented on GitHub (Mar 21, 2024):
Looks like when I set it to
https, I can't access signtools at all. Also, when I setAutomatically redirect to httpsin config,I start receiving
SSL received a record that exceeded the maximum permissible length.when visiting signtools directly (through local ip and port). Possibly this is the issue withhttpsscheme.@ViRb3 commented on GitHub (Mar 21, 2024):
The
X-Forwarded-Protois only used by SignTools for manifest creation andAutomatically redirect to https, if enabled. If SignTools doesn't work at all, you probably have something else in the middle that breaks. I imagine the second error you get is due to infinite redirection if SignTools never seeshttpsin theX-Forwarded-Protoheader. Either way, seems like a problem with your setup, and not SignTools.@ViRb3 commented on GitHub (Apr 25, 2024):
Closing due to inactivity. Hope you got it sorted.