Agent -> Master Connection

[jasonlaguidice]

I tried out Arcane recently and it looks really promising.

Can you set up a reverse connection such that the agent reaches out to the main instance?

Portainer supports this as portainer-edge
Komodo supports this as part of the pending 2.0 version

I have some remote nodes on VPS hosts and do not want to have to expose a port on those hosts. My current setup uses portainer-edge through tailscale for this purpose.

Is this supported in Arcane and I've just missed it in the docs?

[kmendell]

Currently no, i laid some ground work for it a few releasea ago, but i have not found a good way to do it yet. I dont wnat to have a seprate thing for it i want it to be a hybird mode type thing, iots on my radar just havent had the most time to look at it yet.

[jasonlaguidice]

Good to know, I appreciate it anywho!

[kmendell]

I have a working edge based agent, should be ready for 1.14.0

[jasonlaguidice]

That was fast 😂 I'll test!

[jasonlaguidice]

I wanted to return because I've built the main deployment for arcane and have run it - I see the edge agent stuff in there... cool!

I did another build matching the headless type and deployed that on one of my remote machines. I took the token generated from the main and passed it through and... it connects!

The edge environment shows up and the online/offline status works as expected

However when I switch to the edge environment - or at least try to, it fails to connect and I get errors that look a bit like this:

Jan 28 03:14:39.377 INF Incoming request request.method=GET request.host="" request.path=/api/environments/0/settings request.query="" request.params=map[id:0] request.route=/api/environments/:id/settings request.referer="" request.length=0 response.latency=342.283µs response.status=200 response.length=3429

Jan 28 03:14:39.429 INF HTTP error: 401 unauthorized request.method=GET request.host="" request.path=/api/environments/0/containers request.query="start=0&limit=5&sort=created&order=desc" request.params=map[id:0] request.route=/api/environments/:id/containers request.referer="https://arcane.domain.org/login?redirect=%2Fdashboard" request.length=0 response.latency=149.322µs response.status=401 response.length=142

Jan 28 03:14:39.448 INF Incoming request request.method=GET request.host="" request.path=/api/environments/0/settings request.query="" request.params=map[id:0] request.route=/api/environments/:id/settings request.referer="" request.length=0 response.latency=326.203µs response.status=200 response.length=3429

Very likely something I have setup wrong, and of course, I understand the feature isn't complete yet. But I wanted to provide the feedback.

[jasonlaguidice]

I'll provide what feedback I can. On my setup I have the arcane instance behind a reverse proxy that takes care of TLS

I setup the connect address for the edge agent -> master to be the ip address, and http... so it's at http://192.168.1.61:3552

The 401 errors are coming from the log of the edge agent when I select the edge agent environment from the picker

In the browser I see:

CG2WSiiR.js:3 GET https://arcane.domain.org/api/environments/02fb5e63-188a-4551-bf78-0bd690a0658d/containers?start=0&limit=5&sort=created&order=desc 401 (Unauthorized)

[kmendell]

Make sure the reverse proxy allows websockets as that's how the edge agent connects

[jasonlaguidice]

The reverse proxy is traefik and should be good to go for websockets - or at least it is for the other projects I'm playing with which require websockets. If there's any other more verbose logging I can turn on I can try.

[nickbock]

I'm encountering the same issue. Also, when bypassing Traefik, so that doesn't seem to be the issue.

[zandershah]

I'm also running into this error without a reverse proxy