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

Hostname settings #27

Open
michzimny opened this issue Feb 6, 2019 · 3 comments
Open

Hostname settings #27

michzimny opened this issue Feb 6, 2019 · 3 comments
Assignees

Comments

@michzimny
Copy link
Member

In CERNBOX.yaml, the setting CERNBOXGATEWAY_HOSTNAME says that it should match the name of the machine where the proxy is deployed. My understanding is that is the internal hostname of the host that is accessible for instance by hostname command. It does not necessarily relate to domain name that is used in URL addresses.

On the other hand, the setting HOSTNAME says that it is to be used in URL addresses.

Thus, I've set:

  • CERNBOXGATEWAY_HOSTNAME=my_local_host_no_555
  • HOSTNAME=something.up2university.eu

Please assume that something.up2university.eu is a valid domain name set up in DNS. And my_local_host_no_555 is not.

Trying to access the instance, the following happens:

HTTP Request:
GET https://something.up2university.eu/cernbox/index.php

HTTP Response:

302 Found
Location: https://my_local_host_no_555/cernbox/index.php/login

And my web browser does not know what is my_local_host_no_555.

Tested with branch webng_beta_psnc from the upstream.

Am I doing something wrong?

@michzimny
Copy link
Member Author

And when I set both the variables to the public domain name (i.e. something.up2university.eu in my example), it seems to work.

So, is removing the comment for CERNBOXGATEWAY_HOSTNAME a solution for my issue? :)

@diocas
Copy link
Collaborator

diocas commented Feb 7, 2019

Hi Michal,
Yes, in the default config, these are supposed to have the same value.
Did you have any problem migrating the ScienceBox to the new version? This was not changed, so it should be the same config as you had before.

@michzimny
Copy link
Member Author

michzimny commented Feb 7, 2019

Ok, thanks. So perhaps the comment could be changed :)

I have managed to deployed a new instance from scratch using that branch (but without Up2U SSO), but I have not managed to upgrade the existing instance. I have a bunch of observations that I'm going to share with you, hopefully till tomorrow.

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