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

Redirection problem #393

Closed
pcornier opened this issue Dec 19, 2017 · 5 comments
Closed

Redirection problem #393

pcornier opened this issue Dec 19, 2017 · 5 comments
Assignees
Labels
issue: help wanted severity: high If it breaks the basic use of the product

Comments

@pcornier
Copy link

Node.js version: 8.9.3
npm version: 5.5.1
Strapi version: 3.0.0-alpha.7.2
Operating system: Ubuntu 16.04

It seems not possible to create the first user after moving Strapi to production.

I installed Nginx and redirected port 80/443 to localhost:1337 but when I try to access:
https://mydomain.org/admin

I'm redirected to:
https://mydomain.org/http://localhost:1337/admin/plugins/users-permissions/auth/register

@Aurelsicoko
Copy link
Member

Did you set the host domain in your build configuration (see the documentation)? You will need to rebuild the administration panel then.

@pcornier
Copy link
Author

I was able to access the administration today:

  • I re-installed everything
  • I changed my config (just changed host in server.js)
  • then I ran npm install in root directory and in admin directory.

I'm not quite sure I understand why it started to work - the only thing I changed is the configuration file that was edited before running npm install - so I think this should be tested again by someone else and clearly written somewhere.

@Aurelsicoko
Copy link
Member

The administration needs to know the host (IP or domain) to work well. I've added a new section in the documentation to explain How to deploy.

@franzos
Copy link

franzos commented Jan 9, 2018

This relates to #423. Even with the correct settings and rebuild, the admin panel remains inaccessible.

@Aurelsicoko
Copy link
Member

Aurelsicoko commented Jan 10, 2018

It should be fixed in the next release with these changes #431

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: help wanted severity: high If it breaks the basic use of the product
Projects
None yet
Development

No branches or pull requests

4 participants