anyone having issues with accessing chainlink dashboard UI through https?
stuffs that were done:
>followed docs.chain.link
>added custom TCP and UDP connection for port 6688 & 6689 in aws security group. IP source set to all.
worked fine when testing on local machine last night, never touched aws before so not sure what I may have missed
ROOT=/chainlink
LOG_LEVEL=debug
ETH_URL=wss://cl-ropsten.fiews.io/v1/samepleapikey
ETH_CHAIN_ID=3
MIN_OUTGOING_CONFIRMATIONS=2
MIN_INCOMING_CONFIRMATIONS=0
LINK_CONTRACT_ADDRESS=sampleaddress
ALLOW_ORIGINS=*
TLS_CERT_PATH=/chainlink/tls/server.crt
TLS_KEY_PATH=/chainlink/tls/server.key
when I set mine up, I had to set it to debug mode and use http to get dashboard to work
thanks, seems like warosu is down atm so will try it later
The cert that gets created from the chain.link docs is for local access only. To use https on AWS you need to get a real certificate from somewhere like letsencrypt.org.
im a fucking idiot, TLS cert path was wrong (.chainlink-ropsten instead)
yet it's still not working AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
pic related, have made sure to allow custom TCP and UDP port but ping.eu
Your OP pic is an "invalid cert". Your second pic is "can't be reached". You broke something in the second pic
deleted everything and started fresh, this time following fiew's guide carefully. Not going to touch https for the moment.
yet it's still inaccessible even on http
is it because brave browser/ chrome automatically alters http:// to https:// ?
>ALLOW_ORIGINS=*
wew lad
Well this is another completely different error that's usually browser related. If you can get back to the OP pic you can just accept the warning and the dashboard should come up with http and say "not secure"
This looks like a thread for Jow Forums
Here we just shitpost about scams sorry for the confusion
Follow the instructions here docs.chain.link
Buddy are you here? On that screen click through "advanced" and click "show anyway"
let the eth node sync you dunce
Where are you hosting OP
docs.chain.link
Ignore these
If you run locally they'll work. If you try to connect to a remote machine. ie. AWS then it will fail with an invalid cert because Chrome will not accept a self-signed cert anymore. You could also try Firefox and accept the exception.
what command are you using to start the site?
Did you modify the config to be in DEV mode, that is only way http-only works
Accepting the connection via Firefox was not ideal, you want a publicly valid certificate long term. Since you are on aws, you don't own the IP. I would buy a domain name OP. Easiest way.
Yes, if you want a production setup buy a domain and get a real cert. But since mainnets not out yet it's kinda pointless right now. Just get to the dashboard by whatever works for testing.
cheers anons. Turns out some browsers just ignores http requests and converts them to https.
Used vivaldi and dashboard showed up. adding /signin to the end of your address works too
hopefully configuring for https would go smoothly...
Just know how to set up a domain for your instance before mainnet, not hard but worth looking at if you've never done it.
If he struggled with this he's not going to figure out how to set up a domain for his node.
tldr:
>make sure to set CHAINLINK_DEV=true in .env for http
>custom UDP and TCP port on 6688 in aws security group
>try different browsers
not going to touch https for now, shit just keeps breaking. pretty comfy learning process overall
cheers
k3k