Autossh sometimes fails to start when internet is not ready, e.g. Hass.io and router start at the same time after power failure and router takes more time to connect to internet. Autossh can handle this with env variables (AUTOSSH_GATETIME) but there's no way to define them in the add-on.

frpc addon does not have 'arch' in config.json, supervisor shows:

WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/03351470/frpc/config.json: required key not provided @ data['arch']. Got None

After adding repository and clicking 'Install', nothing happens.

hass.io 0.58.1 on RasPi 3

Hey there!
I just tested your addon and it worked right out of the box. Used it to forward my local HA server to a publicly reachable server, there a reverse proxy (caddy) takes care of serving the webpage from 127.0.0.1 with Let's Encrypt certificate. The whole thing took me 15min to set up. Amazing. Thanks!

I've created this ticket to ask if there is a specific reason why you decided to not (or not yet) add this project to the official addons repository. I would be happy to help where I can.

Hi there

I 'm trying to use autossh on my hassio on ubuntu/docker install.. I restored my backup (previously running on raspy) and I can see your repository among the ones I had, but no addons from you are available.

AFAICS, the issue is because your addons are missing the
"arch": ["armv7", "armhf", "amd64", "aarch64", "i386"],
key in config.json

I'm suffering the same issues with other addons as well, coming from other repos

It works fine but when there is any interruption in the internet connection then it doesn't reconnect.

Here is the log

debug1: Authentication succeeded (publickey).
Authenticated to 139.59.13.23 ([139.59.13.23]:22).
debug1: Remote connections from LOCALHOST:3000 forwarded to local address localhost:8123
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug1: remote forward success for: listen 3000, connect localhost:8123
debug1: All remote forwarding requests processed
debug1: client_input_channel_open: ctype forwarded-tcpip rchan 2 win 2097152 max 32768
debug1: client_request_forwarded_tcpip: listen localhost port 3000, originator 127.0.0.1 port 43972
debug1: connect_next: host localhost ([::1]:8123) in progress, fd=4
debug1: channel 0: new [127.0.0.1]
debug1: confirm forwarded-tcpip
debug1: channel 0: connection failed: Connection refused
debug1: connect_next: host localhost ([127.0.0.1]:8123) in progress, fd=5
debug1: channel 0: connected to localhost port 8123
debug1: channel 0: free: 127.0.0.1, nchannels 1
debug1: client_input_channel_open: ctype forwarded-tcpip rchan 2 win 2097152 max 32768
debug1: client_request_forwarded_tcpip: listen localhost port 3000, originator 127.0.0.1 port 43974
debug1: connect_next: host localhost ([::1]:8123) in progress, fd=4
debug1: channel 0: new [127.0.0.1]
debug1: confirm forwarded-tcpip
debug1: channel 0: connection failed: Connection refused
debug1: connect_next: host localhost ([127.0.0.1]:8123) in progress, fd=5
debug1: channel 0: connected to localhost port 8123
debug1: channel 0: free: 127.0.0.1, nchannels 1

Any reason why it stops trying after connection is refused twice?
It fails twice cause internet takes some time to start working again.

Hi,

When I disconnect the rpi to the internet cable and reconnect it after some hours, the connection is working.
When I restart the Home Assistant, it is working too.

But, when I power off the rpi, I have a bad gateway.
Here is my configuration :

`hostname: home-assistant.example.com
ssh_port: '22'
username: user
remote_forwarding:

• '172.17.0.1:44400:172.17.0.1:8123'
  local_forwarding:
• ''
  other_ssh_options: '-o "ExitOnForwardFailure yes"'
  monitor_port: '0'
  gatetime: '30'
  `

Is there something I forget ?

Thanks