Can't access wp-admin dashboard

I have setup a wordpress dev environment with trellis. Now want wo develop a theme with sage. Everything seems to work fine, but when trying to use bud I cannot log into the dashboard.

I tried to get a bit more of an idea whats going on: yarn dev --log --verbose --no-cache

When accessing http://0.0.0.0:3000 this it the output:

[99%] [cache] begin idle
❯  firing action event.compiler.done 1/2
❯  firing action event.compiler.done 2/2
[http] › ❯  [200] /wp-admin 
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
ℹ  /wp-admin null text/html; charset=UTF-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/css/dashicons.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-includes/css/buttons.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-admin/css/l10n.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-admin/css/login.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-admin/css/forms.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-includes/js/jquery/jquery.js?ver=3.6.0 
ℹ  /wp/wp-includes/css/buttons.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/jquery/jquery-migrate.js?ver=3.3.2 
ℹ  /wp/wp-includes/css/dashicons.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/zxcvbn-async.js?ver=1.0 
ℹ  /wp/wp-admin/css/l10n.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
ℹ  /wp/wp-admin/css/login.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/dist/vendor/regenerator-runtime.js?ver=0.13.9 
[http] › ❯  [200] /wp/wp-includes/js/dist/vendor/wp-polyfill.js?ver=3.15.0 
ℹ  /wp/wp-admin/css/forms.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/dist/hooks.js?ver=1e58c8c5a32b2e97491080c5b10dc71c 
ℹ  /wp/wp-includes/js/zxcvbn-async.js?ver=1.0 null application/javascript; charset=utf-8
ℹ  /wp/wp-includes/js/jquery/jquery.js?ver=3.6.0 null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-includes/js/dist/i18n.js?ver=30fcecb428a0e8383d3776bcdd3a7834 
ℹ  /wp/wp-includes/js/jquery/jquery-migrate.js?ver=3.3.2 null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-admin/js/password-strength-meter.js?ver=5.9.2 
[http] › ❯  [200] /wp/wp-includes/js/underscore.min.js?ver=1.13.1 
ℹ  /wp/wp-includes/js/dist/vendor/regenerator-runtime.js?ver=0.13.9 null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-admin/js/user-profile.js?ver=5.9.2 
ℹ  /wp/wp-includes/js/dist/vendor/wp-polyfill.js?ver=3.15.0 null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-includes/js/wp-util.js?ver=5.9.2 
ℹ  /wp/wp-includes/js/dist/hooks.js?ver=1e58c8c5a32b2e97491080c5b10dc71c null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-admin/images/wordpress-logo.svg?ver=20131107 
ℹ  /wp/wp-includes/js/dist/i18n.js?ver=30fcecb428a0e8383d3776bcdd3a7834 null application/javascript; charset=utf-8
ℹ  /wp/wp-includes/js/underscore.min.js?ver=1.13.1 null application/javascript; charset=utf-8
ℹ  /wp/wp-admin/js/password-strength-meter.js?ver=5.9.2 null application/javascript; charset=utf-8
ℹ  /wp/wp-admin/js/user-profile.js?ver=5.9.2 null application/javascript; charset=utf-8
ℹ  /wp/wp-includes/js/wp-util.js?ver=5.9.2 null application/javascript; charset=utf-8
ℹ  /wp/wp-admin/images/wordpress-logo.svg?ver=20131107 null image/svg+xml
[http] › ❯  [200] /favicon.ico 
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
ℹ  /favicon.ico null image/png

Entering my credentials, trying to login…

[http] › ❯  [200] /wp/wp-login.php 
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
ℹ  /wp/wp-login.php null text/html; charset=UTF-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/css/dashicons.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-includes/css/buttons.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-admin/css/forms.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-admin/css/l10n.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-admin/css/login.css?ver=5.9.2 
[http] › ❯  [200] /wp/wp-includes/js/jquery/jquery.js?ver=3.6.0 
ℹ  /wp/wp-includes/css/dashicons.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
ℹ  /wp/wp-admin/css/forms.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/jquery/jquery-migrate.js?ver=3.3.2 
[http] › ❯  [200] /wp/wp-includes/js/zxcvbn-async.js?ver=1.0 
ℹ  /wp/wp-includes/css/buttons.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/dist/vendor/regenerator-runtime.js?ver=0.13.9 
ℹ  /wp/wp-admin/css/l10n.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/dist/vendor/wp-polyfill.js?ver=3.15.0 
ℹ  /wp/wp-admin/css/login.css?ver=5.9.2 null text/css; charset=utf-8
❯  firing action event.proxy.interceptor 1/2
❯  firing action event.proxy.interceptor 2/2
[http] › ❯  [200] /wp/wp-includes/js/dist/hooks.js?ver=1e58c8c5a32b2e97491080c5b10dc71c 
ℹ  /wp/wp-includes/js/zxcvbn-async.js?ver=1.0 null application/javascript; charset=utf-8
ℹ  /wp/wp-includes/js/jquery/jquery.js?ver=3.6.0 null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-includes/js/dist/i18n.js?ver=30fcecb428a0e8383d3776bcdd3a7834 
ℹ  /wp/wp-includes/js/jquery/jquery-migrate.js?ver=3.3.2 null application/javascript; charset=utf-8
ℹ  /wp/wp-includes/js/dist/vendor/regenerator-runtime.js?ver=0.13.9 null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-admin/js/password-strength-meter.js?ver=5.9.2 
[http] › ❯  [200] /wp/wp-includes/js/underscore.min.js?ver=1.13.1 
[http] › ❯  [200] /wp/wp-includes/js/wp-util.js?ver=5.9.2 
ℹ  /wp/wp-includes/js/dist/vendor/wp-polyfill.js?ver=3.15.0 null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-admin/js/user-profile.js?ver=5.9.2 
ℹ  /wp/wp-includes/js/dist/hooks.js?ver=1e58c8c5a32b2e97491080c5b10dc71c null application/javascript; charset=utf-8
[http] › ❯  [200] /wp/wp-admin/images/wordpress-logo.svg?ver=20131107 
ℹ  /wp/wp-includes/js/dist/i18n.js?ver=30fcecb428a0e8383d3776bcdd3a7834 null application/javascript; charset=utf-8
ℹ  /wp/wp-admin/js/password-strength-meter.js?ver=5.9.2 null application/javascript; charset=utf-8
ℹ  /wp/wp-includes/js/wp-util.js?ver=5.9.2 null application/javascript; charset=utf-8
ℹ  /wp/wp-includes/js/underscore.min.js?ver=1.13.1 null application/javascript; charset=utf-8
ℹ  /wp/wp-admin/js/user-profile.js?ver=5.9.2 null application/javascript; charset=utf-8
ℹ  /wp/wp-admin/images/wordpress-logo.svg?ver=20131107 null image/svg+xml
[http] › ❯  [200] /favicon.ico 
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
ℹ  /favicon.ico null image/png

Not ending up in the dashboard but on http://0.0.0.0:3000/wp/wp-login.php. If I try again from here, same same…

The dashboard works fine, when using the proxy URL: http://wesf.test/wp-admin/

Anyone else experiencing similar issue?

Thank you and have a great day,
Hans

Once you’ve landed on http://0.0.0.0:3000/wp/wp-login.php open your browser devtools and delete any stored cookies / application data. Refresh the page. You should see WordPress complaining that your browser doesn’t support cookies. Any cookies that you do see should have the 0.0.0.0 hostname.

From there you should be able to log in.

1 Like

Thank you so much. Instant fix!

For others – see attached screenshot where to click:

1 Like