abra server add can't handle "remote" LAN connects #279

Closed
opened 2021-12-01 11:19:03 +00:00 by decentral1se · 1 comment
Owner
➜  ~ abra server add -p thing.local local 222
INFO[0000] successfully created /home/decentral1se/.abra/servers/thing.local 
FATA[0010] dial tcp 192.168.178.36:222: i/o timeout  

Work-around is to pass --nd. Error message should reflect this.

``` ➜ ~ abra server add -p thing.local local 222 INFO[0000] successfully created /home/decentral1se/.abra/servers/thing.local FATA[0010] dial tcp 192.168.178.36:222: i/o timeout ``` Work-around is to pass `--nd`. Error message should reflect this.
decentral1se added the
bug
abra
labels 2021-12-01 11:19:03 +00:00
decentral1se added this to the (deleted) project 2022-10-22 12:29:35 +00:00
decentral1se added the
good first issue
label 2022-10-22 12:34:34 +00:00
Author
Owner

This is still the case actually, despite the server add interface and logic changing in coop-cloud/abra#255. The add still demands that it's a public domain name. We discussed this and it seems like a pretty hard requirement basically because you typically are also doing LE certs and public routing. We can imagine all sorts of other configurations but maybe those are for another tool...

This is still the case actually, despite the `server add` interface and logic changing in https://git.coopcloud.tech/coop-cloud/abra/pulls/255. The add still demands that it's a public domain name. We discussed this and it seems like a pretty hard requirement basically because you typically are also doing LE certs and public routing. We can imagine all sorts of other configurations but maybe those are for another tool...
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#279
No description provided.