-
Notifications
You must be signed in to change notification settings - Fork 74
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
Comments
@ryelle in response to your suggestion in Slack to create the site without the year, I was not able to do this initially. I was able to comment the wp_die() line below to get around this.
While I'm unblocked on creating the new site, I still feel there is an issue to be investigated here. |
@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. |
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! |
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
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
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
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
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
I think #933 may have fixed this. Do you mind testing a fresh install? |
Tested with the new data, and worked as expected. I was able to access the admin for existing and new sites. |
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:
Ryan 2022
.https://ryan.wordcamp.test/2022/
), check the box toCreated site in network
, and change the status toNeeds Crowdsignal Account
./etc/hosts
file an entry for my WordCamp. Mine isAttached 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
System (please complete the following information):
The text was updated successfully, but these errors were encountered: