Chenlink noeds

anyone having issues with accessing chainlink dashboard UI through https?

stuffs that were done:
>followed docs.chain.link/docs/enabling-https-connections
>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

Attached: https.png (1366x768, 42K)

Other urls found in this thread:

warosu.org/biz/thread/13326565#p13330892
ping.eu/port-chk/
docs.chain.link/docs/enabling-https-connections
docs.chain.link/docs/running-a-chainlink-node
twitter.com/NSFWRedditImage

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

warosu.org/biz/thread/13326565#p13330892

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

Attached: https.png (1366x768, 44K)

pic related, have made sure to allow custom TCP and UDP port but ping.eu/port-chk/ shows 6689 and 6688 ports on my instance IP as closed

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

Attached: https.png (857x429, 16K)