"This account is currently not available" error

[aleinside]

Hi Michele,
I'm trying your project but trying butterfly, after the ec2 instance configuration, I got the "This account is currently not available" error for ssh.
Do you have any hint to solve this issue?

Thank you!

[sciabarra]

Not sure to understand the issue.... Il 24/01/17 18:41, Alessandro Nuzzo ha scritto:

…

Hi Michele, I'm trying your project but trying butterfly, after the ec2 instance configuration, I got the "This account is currently not available" error for ssh. Do you have any hint to solve this issue? Thank you! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAhHiaUOAzd2bRs9C11T2Zzl91cyjHEeks5rVje3gaJpZM4LskPk>.

-- *Michele Sciabarra - CEO* /Sciabarra.com limited/ 20-22 Bedford Row WC1R 4JS London, United Kingdom Company Number 873731 Registered in England and Wales Tel: +44 7479 848388 Email: [email protected] <mailto:[email protected]> Skype: michele.sciabarra Linkedin: uk.linkedin.com/in/msciab <http://uk.linkedin.com/in/msciab>

[aleinside]

I follow instructions in your article to configure the aws instance. I used ami-init.sh to install and configure the server on startup, as explained. When I visit my host I received from butterfly the error "This account is currently not available". Maybe there is a problem with the nginx reverse proxy configuration, as reported in this issue paradoxxxzero/butterfly#7 I'm able to login with the app user through ssh with the choiced password. 2017-01-25 18:40 GMT+01:00 Michele Sciabarra <[email protected]>:

…

Not sure to understand the issue.... Il 24/01/17 18:41, Alessandro Nuzzo ha scritto: > > Hi Michele, > I'm trying your project but trying butterfly, after the ec2 instance > configuration, I got the "This account is currently not available" > error for ssh. > Do you have any hint to solve this issue? > > Thank you! > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#1>, or mute the > thread > <https://github.com/notifications/unsubscribe-auth/ AAhHiaUOAzd2bRs9C11T2Zzl91cyjHEeks5rVje3gaJpZM4LskPk>. > -- *Michele Sciabarra - CEO* /Sciabarra.com limited/ 20-22 Bedford Row WC1R 4JS London, United Kingdom Company Number 873731 Registered in England and Wales Tel: +44 7479 848388 <+44%207479%20848388> Email: ***@***.*** ***@***.***> Skype: michele.sciabarra Linkedin: uk.linkedin.com/in/msciab <http://uk.linkedin.com/in/msciab> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABvu82CDk1e3lLyn3bAvxeuR14lumVVUks5rV4kQgaJpZM4LskPk> .

[sciabarra]

You may be right. It is possible butterfly got updated (scripts are using the latest version) so probably also the reverse proxy need to be updaetd. Hope to have some time soon to check it. In the meanwhile you can fork the project, patch the configuration in the ami-init.sh and use your url to initialize the image.