-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Description
Hi.
I'm interested in setting up a tunnel to localhost.run.
Running their command line examples work great, and as advertised.
R-stuff ssh -R 80:localhost:1313 nokey@localhost.run
===============================================================================
[...]
** your connection id is 26493725-4c74-4375-94c1-293a63b33a18, please mention it if you send me a message about an issue. **
f27f2133f61afa.localhost.run tunneled with tls termination, https://f27f2133f61afa.localhost.runand I can see whatever I'm serving on that localhost port at the url provided.
I'm trying to set up this infrastructure using this package, but am not managing properly.
problems:
I dont think the tunnel is set up correctly by my settings. The unique url is not outputted by the call I'm doing, which is why I'm not convinced I've done as the service requires. But it is also not erroring, so I'm not sure.
I need to capture the unique url to use as an oAuth redirect.
proc <- callr::r_bg(function(){
session <- ssh::ssh_connect("nokey@localhost.run")
ssh::ssh_tunnel(session, 8080, "localhost.run:80")
})
> proc$read_all_output()
[1] "\n** your connection id is e1e78880-c784-44be-9cee-90eab314a46b, please mention it if you send me a message about an issue. **\n\n\n"Any tip is appreciated, I'm pretty new to this. I'm using the call suggested by #13
Metadata
Metadata
Assignees
Labels
No labels