Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server url is not correct #1

Open
chrisabad-zz opened this issue Apr 22, 2015 · 4 comments
Open

Server url is not correct #1

chrisabad-zz opened this issue Apr 22, 2015 · 4 comments

Comments

@chrisabad-zz
Copy link

I keep getting this error, and I'm not sure why. We're on a cloud-based account, so our URL looks like "https://xxxxxx.hipchat.com"

@schnej7
Copy link
Owner

schnej7 commented Apr 26, 2015

You are getting this error "Server url is not correct, are you missing 'https://' ?"?

The install script tries to curl that url and check that the status is 200 to make sure it is reachable from wherever you are trying to install from. What you enter for this step should be exactly what is in the URL bar when you browse to your hipchat server.

@chrisabad-zz
Copy link
Author

Looks like Hipchat doesn't return a 200 (at least for me). It returns a 403 Unauthorized status. I made a change in the source code and everything looks fine.

@moises-silva
Copy link

@chrisabad For cloud instances the server url should be https://api.hipchat.com/

@schnej7 The first check in the install script will return 403 (actually 302) for cloud instances. Using curl -L should allow follow the redirect, but still, the first check returns 403 anyways, so for cloud instances seems you can just skip the first check and go to the second (that one works).

It worked for me mostly, unfortunately for whatever reason one of my rooms didn't display anything at all (blank), worked on the other rooms though. Unfortunately I had to revert the changes, didn't really have time to check why that one room was displaying a blank chat page.

@schnej7
Copy link
Owner

schnej7 commented Dec 30, 2015

I have seen that before, @moises-silva. I think that should be filed as a separate issue.

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

No branches or pull requests

3 participants