You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2021. It is now read-only.
Hello!
I'm doing the setup from a MacBook. The password I created on instapy.io contains special characters...😬
When running setup.sh, I enter the username and passwords I set on instapy.io. But when I run startClient.sh, it says Passwords do not match.
I think this is because of one of the special characters, which is a little too special (I used a password generator...sawry). The problem is that I can't change my password on instapy.io.
I've found a workaround by hardcoding it directly into setup.sh and escaping the special chars, but I just wanted to let you know about this issue.
Cheers all! Your work is awesome.
❤️
The text was updated successfully, but these errors were encountered:
vm00z
changed the title
Passwords with special characters breaks things
Password with special characters breaks things
Dec 1, 2020
one thing could help me here: what is the special character that you have to escape ?
/edit could you check if the password in the file .env is also escaped or not ? and one last question, if you delete .env file and start setup.sh again and escape it while inserting in the command line, does it work then ?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
I'm doing the setup from a MacBook. The password I created on instapy.io contains special characters...😬
When running setup.sh, I enter the username and passwords I set on instapy.io. But when I run startClient.sh, it says
Passwords do not match
.I think this is because of one of the special characters, which is a little too special (I used a password generator...sawry). The problem is that I can't change my password on instapy.io.
I've found a workaround by hardcoding it directly into setup.sh and escaping the special chars, but I just wanted to let you know about this issue.
Cheers all! Your work is awesome.
❤️
The text was updated successfully, but these errors were encountered: