Skip to content
This repository has been archived by the owner on Jan 10, 2022. It is now read-only.

weird behavior while installastion in ubuntu (some type of string escaping errors) #266

Closed
chandanpasunoori opened this issue Dec 5, 2014 · 5 comments

Comments

@chandanpasunoori
Copy link

if installation pass has any forward slash / then installation form not accepting it, and not going further but if it has no forwards slash then it accepting

and even though mongodb url is given correctly its getting error like

5 Dec 19:51:04 - error: Unable to connect to the specified database mongodb://localhost:27017/calipso, the problem was: failed to connect to [mongodb:27017]

image

image

@richtera
Copy link
Collaborator

richtera commented Dec 5, 2014

Did you install mongo on your server and start it? Alternatively you can
provide a MONGO_URI environment variable. Do you have an old config file or
is there a bug that tries to connect before you can configure the database
url?
Andy

Sent from my iPhone

On Dec 5, 2014, at 9:29 AM, ETS REPO notifications@github.com wrote:

if installation pass has any forward slash / then installation form not
accepting it, and not going further but if it has no forwards slash then it
accepting

and even though mongodb url is given correctly its getting error like

5 Dec 19:51:04 - error: Unable to connect to the specified database
mongodb://localhost:27017/calipso, the problem was:
failed to connect to [mongodb:27017]

[image: image]
https://cloud.githubusercontent.com/assets/3172168/5317004/55112248-7cb8-11e4-8df5-3b22c4fb10a3.png

[image: image]
https://cloud.githubusercontent.com/assets/3172168/5317015/76cc149c-7cb8-11e4-9341-fea346fda705.png


Reply to this email directly or view it on GitHub
#266.

@chandanpasunoori
Copy link
Author

well for mongo its ok for professional user can work on but not normal user

I have installed already

but what about installation password error ...?

did you checked it?

@richtera
Copy link
Collaborator

richtera commented Dec 6, 2014

The installation password is not and error. Basically when you go to the site it will ask for an installation password which has to be the one in the application's log. What do you mean "normal user"? Calipso only runs when it's connected to a mongodb instance. The password protects you from someone else setting up your site when you're hosting it. Only the person that has access to the console log will know the password.
Does that make sense or are you still stuck?
Thanks
Andy

On Dec 6, 2014, at 7:56 AM, ETS REPO notifications@github.com wrote:

well for mongo its ok for professional user can work on but not normal user

I have installed already

but what about installation password error ...?

did you checked it?


Reply to this email directly or view it on GitHub #266 (comment).

@richtera
Copy link
Collaborator

I have recently seen some kind of / to / conversion in other places as well. I wonder if this is node version specific. I just resolve a similar problem with the installation password by changing it to hex string. I don’t know where an how this conversion is happening.
Andy

On Dec 5, 2014, at 9:29 AM, ETS REPO notifications@github.com wrote:

if installation pass has any forward slash / then installation form not accepting it, and not going further but if it has no forwards slash then it accepting

and even though mongodb url is given correctly its getting error like

5 Dec 19:51:04 - error: Unable to connect to the specified database mongodb://localhost:27017/calipso, the problem was: failed to connect to [mongodb:27017]

https://cloud.githubusercontent.com/assets/3172168/5317004/55112248-7cb8-11e4-8df5-3b22c4fb10a3.png
https://cloud.githubusercontent.com/assets/3172168/5317015/76cc149c-7cb8-11e4-9341-fea346fda705.png

Reply to this email directly or view it on GitHub #266.

@richtera
Copy link
Collaborator

This was due to a html escape cleanup merged in june. I undid this changed and published.
I am not quite sure what the author wanted to escape fields of type "text" for so I asked what the original reason was so that we can determine whether it makes sense to create a new field type for text that gets escaped or a new field type for text that doesn't get escaped. Thanks for notifying me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants