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

client disregards configured port in some cases #148

Closed
Synthetica9 opened this issue Jul 11, 2024 · 1 comment
Closed

client disregards configured port in some cases #148

Synthetica9 opened this issue Jul 11, 2024 · 1 comment

Comments

@Synthetica9
Copy link

I have an attic server set up with a non-default https port, 4343 in my case. My config looks like this:

default-server = "myserver"

[servers.myserver]
endpoint = "https://myserver.mycompany.com:4343/"
token = "..."

If I then attic push to this, I get the following result after a timeout:

Error: error sending request for url (https://myserver.mycompany.com/_api/v1/get-missing-paths)

Caused by:
    0: client error (Connect)
    1: tcp connect error: Connection timed out (os error 110)
    2: Connection timed out (os error 110)

Somewhere along the way, the port number got discarded.

Paths that are uploaded internally in my network do download correctly.

Is this misconfiguration in my nginx reverse proxy? Bug in attic? A secret third thing?

@Synthetica9
Copy link
Author

Ah, it came from a non-configured api-endpoint it seems, now it works.

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

No branches or pull requests

1 participant