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

Unable to access admin for new WordCamp site in Docker local #782

Closed
CdrMarks opened this issue Jun 13, 2022 · 5 comments
Closed

Unable to access admin for new WordCamp site in Docker local #782

CdrMarks opened this issue Jun 13, 2022 · 5 comments
Labels
[Component] Tooling Build tools, automated testing, source control, linting, etc

Comments

@CdrMarks
Copy link
Collaborator

Describe the bug

After setting up a local environment running using the Docker instructions, and creating a new WordCamp and its site, I was unable to browse to the site.

Blocking: #777

To reproduce

Steps to reproduce the behavior:

  1. Setup your local environment using Docker.
  2. Create a new WordCamp at https://central.wordcamp.test/wp-admin/post-new.php?post_type=wordcamp. Mine was Ryan 2022.
  3. Advance the WordCamp to a status of "Needs Site" and enter any required information.
  4. Fill in the URL field (mine was https://ryan.wordcamp.test/2022/), check the box to Created site in network, and change the status to Needs Crowdsignal Account.
  5. Add to my /etc/hosts file an entry for my WordCamp. Mine is

127.0.0.1 wordcamp.test central.wordcamp.test city.wordcamp.test ryan.wordcamp.test

  1. Browse to https://wordcamp.test/wp-admin/network/sites.php and see the site.
  2. Click on Dashboard under my new site: https://ryan.wordcamp.test/2022/wp-admin/. See the following error:

This page isn’t working
ryan.wordcamp.test redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS

  1. Clear all cookies following the instructions above.
  2. Browse to https://ryan.wordcamp.test/2022/wp-admin/. Continue to see the error
  3. Browse to https://ryan.wordcamp.test/2022/. Can see the new site's public pages without issue.

Attached is a zipped .HAR file.
ryan.wordcamp.test.har.zip

Expected behavior

I would be able to see the /wp-admin interface for the Ryan 2022 WordCamp.

Screenshots

image

image

System (please complete the following information):

  • Device: MBP
  • OS: macOS Monterey 12.4
  • Browser Chrome
  • Version 102.0.5005.115 (Official Build) (x86_64)
@CdrMarks CdrMarks added the [Component] Tooling Build tools, automated testing, source control, linting, etc label Jun 13, 2022
@CdrMarks
Copy link
Collaborator Author

CdrMarks commented Jun 16, 2022

@ryelle in response to your suggestion in Slack to create the site without the year, I was not able to do this initially.

image

I was able to comment the wp_die() line below to get around this.

if ( ! self::url_matches_expected_format( $parsed_url['host'], $parsed_url['path'], $wordcamp_id ) ) {
	//wp_die( 'The URL does not match the expected <code>city.wordcamp.org/year/</code> format. Please press the back button and update it.' );
}

While I'm unblocked on creating the new site, I still feel there is an issue to be investigated here.

@dmkjr
Copy link

dmkjr commented Oct 29, 2022

@CdrMarks Seeing a very similar problem (but not utilizing WordCamp). Can access the site locally but can not access wp_admin after setting up for proxy.

@2ndkauboy
Copy link
Contributor

This is still an ongoing issue and we really need a fix for this if we want to attract community members to contribute to Meta. We were not able to get the environment running at WCAsia 2023 Contributor Day for various reasons and this issue finally prevented us from onboarding new contributors!

2ndkauboy added a commit to 2ndkauboy/wordcamp.org that referenced this issue Feb 20, 2023
The nginx.conf was missing some configuration for backends of individual WordCamps to work then using the year as a subdirectory, which is the default now.

Fixes WordPress#782
2ndkauboy added a commit to 2ndkauboy/wordcamp.org that referenced this issue Feb 20, 2023
The nginx.conf was missing some configuration for backends of individual WordCamps to work then using the year as a subdirectory, which is the default now.

Fixes WordPress#782
2ndkauboy added a commit to 2ndkauboy/wordcamp.org that referenced this issue Feb 20, 2023
The nginx.conf was missing some configuration for backends of individual WordCamps to work then using the year as a subdirectory, which is the default now.

Fixes WordPress#782
2ndkauboy added a commit to 2ndkauboy/wordcamp.org that referenced this issue Feb 20, 2023
The nginx.conf was missing some configuration for backends of individual WordCamps to work then using the year as a subdirectory, which is the default now.

Fixes WordPress#782
2ndkauboy added a commit to 2ndkauboy/wordcamp.org that referenced this issue Apr 16, 2023
The nginx.conf was missing some configuration for backends of individual WordCamps to work then using the year as a subdirectory, which is the default now.

Fixes WordPress#782
@iandunn
Copy link
Member

iandunn commented Jul 6, 2023

I think #933 may have fixed this. Do you mind testing a fresh install?

@timiwahalahti
Copy link
Collaborator

Tested with the new data, and worked as expected. I was able to access the admin for existing and new sites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Component] Tooling Build tools, automated testing, source control, linting, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants