This is a standard install . These credentials work on the old server and they work on the new server using s3cmd, but when I do a discourse restore to try to get a list of backups, I get Error retrieving instance profile credentials: Failed to open TCP connection to 169.254.169.254:80 (execution ex…

[이미지] pfaffman: Failed to open TCP connection to 169.254.169.254 The AWS client is attempting to connect to the EC2 metadata service to retrieve its instance profile credentials. If that worked, it would then use these credentials to attempt to connect to the bucket. But, it can’t connect t…

s3 문제: 시크릿 액세스 키가 없어 169.254.169.254에 대한 TCP 연결을 열지 못함

지원 자체 호스팅

pfaffman (Jay Pfaffman) 3월 23, 2025, 4:18오후 3

OMG. I thought I was going crazy.

I had

DISCOURSE_S3_SECRET_ACCESS=xxx

rather than

DISCOURSE_S3_SECRET_ACCESS_KEY=xxx

글		댓글	조회수
Failed to open TCP connection to <my-site>.s3.amazonaws.com:443 Support	6	5862	10월 23, 2019
Issues backing up to s3 Self-hosting backups , s3	4	1036	2월 9, 2018
AWS S3 upload - unable to sign request without credentials set Support	5	338	12월 17, 2024
Discourse instance unreachable on AWS Support	27	4202	2월 8, 2017
Backups to S3 fail when IMDSv1 disabled Bug backups , s3	0	112	8월 29, 2024

s3 문제: 시크릿 액세스 키가 없어 169.254.169.254에 대한 TCP 연결을 열지 못함

Related topics