[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

View post   
File: 42 KB, 400x323, 1526854949637.jpg [View same] [iqdb] [saucenao] [google]
15747196 No.15747196 [Reply] [Original]

I created a node on a Google cloud server but I am too stupid to connect to the GUI can somebody help pls?

>> No.15747222

>>15747196
Doesn't exist yet

>> No.15747249
File: 7 KB, 250x174, q5OL30Eh.jpg [View same] [iqdb] [saucenao] [google]
15747249

>>15747222
Checked but fuck off from my thread you disgusting nulinker, the absolute state of this board. Now can somebody help me or not? I have problems creating a ssh tunnel in Ubuntu, I am too stupid for this shit

>> No.15747251

>>15747196
Hi Jok

>> No.15747298
File: 825 KB, 700x700, 4d7.png [View same] [iqdb] [saucenao] [google]
15747298

>>15747251
Reported for doxxing

>> No.15747334

>>15747249
Having tve same problem. I just get connection refused error. My node isnt finished yet tho, so idk

Have you made the exception in the firewall?

>> No.15747359

>>15747334
I tried adding the external ip of the node to the firewall but it didn't work either so I am not sure I did it right...

>> No.15747446

>>15747249
I only know how to do it in AWS with putty and windows

>> No.15747481
File: 272 KB, 975x600, hackerman.jpg [View same] [iqdb] [saucenao] [google]
15747481

>>15747298
this is hackerman you faggot

>> No.15747495

>>15747359
I guess we have the same problem then. Ur node done with the headers?

>> No.15747499

>>15747196
Follow this guide since nobody is actually gonna bother to help you

https://medium.com/@devlin.trace/idiots-guide-chainlink-node-in-aws-21994b71fa92

Part 3 I believe, has the info you seek

>> No.15747572

>>15747196
>>15747499

That's good guide but he's failing to explain a few things. This was one of those. They mention it better in the Chainlink docs.

Basically you need to do "local port tunneling". Here was the command I used:

ssh -N -L 6689:localhost:6689 -i LINK_NODE_1_KEY.pem admin@xxxxxxxxxxxx.us-east-2.compute.amazonaws.com

Then I could access the GUI through that port on localhost

Godspeed anon

>> No.15747586

>>15747572
Thanks and where do I get the info to put in that command? I guess the api email but what else?

>> No.15747597

>>15747196
there isn't a GUI

>> No.15747619

>>15747597
There is

>> No.15747657

>>15747586
No, on the right is simply the username and url to my server.

The PEM file was given by AWS when I created my instance. You got anything similar?