# Install failed - Container SSH failed to find authorized keys **URL:** https://meta.discourse.org/t/install-failed-container-ssh-failed-to-find-authorized-keys/359280 **Category:** Support **Created:** [March 28, 2025, 12:56pm UTC](https://meta.discourse.org/t/install-failed-container-ssh-failed-to-find-authorized-keys/359280 "2025-03-28T12:56:59Z") **Posts on this page:** 1 **Page:** 1
### Author: ![geoff777](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/geoff777/32/202388_2.png) [@geoff777](https://meta.discourse.org/u/geoff777) #### Post date: [March 28, 2025, 12:56pm UTC](https://meta.discourse.org/t/install-failed-container-ssh-failed-to-find-authorized-keys/359280/1 "2025-03-28T12:56:59Z")
I’m getting a problem installing discourse. Authorized keys not found. I believe this is an legacy way to access a container, no longer needed. I can comment out the last line of web\_only.yml which works. But this is only possible on a second pass after web\_only is populated/created. By then the install has failed and discourse doctor reports instance not found. Rebuilding doesn’t make any difference. Had so many attempts I got temp blocked by Lets Encrypt. OK today. I used to do these installs in my sleep ..lol. 72 hours and nothing but failures. Doesn’t seem to be an answer. Catch 22?