Skip to content

[Bug]: Running OpenSign on custom port does not work - api calls ignore port #1936

@kuermayr-inola

Description

@kuermayr-inola

Issue Description

Hello,
we added a custom port to the opensign URL via .env.prod config today.
The port is open in our firewall and the tool can be accessed from the public internet (dashboard can be reached).
All good - BUT
in the document creation dialog (and probably some other places) opensign calls for the api and does not include/ignores the configured custom port. The api call goes into timeout because 443 is blocked by the firewall.

Internally within our network opensign works fine.

Is there any possibility to enforce the port for the api calls?

mentioned api call which fails:
https://opensign.inola.at/api/app/files/opensign/ea58780a15bced195989926dd1de990e_Georg_008.jpg?token=XYZ

Expected Behavior

No response

Current Behavior

No response

Steps to reproduce

No response

Screenshots of the issue(optional)

No response

Operating System [e.g. MacOS Sonoma 14.1, Windows 11]

No response

What browsers are you seeing the problem on?

Chrome

What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]

2.27.2

What environment are you seeing the problem on?

Production (app.opensignlabs.com), Hosted (app.yourdomain.com)

Please check the boxes that apply to this issue report.

  • I have searched the existing issues & discussions to make sure that this is not a duplicate.

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I have searched the existing issues & discussions to make sure that this is not a duplicate.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions