Randy Fay

Could you share with me what was in the .ddev/traefik.bak? A tarball/zipball would be great. Sorry about the malware spammer in this issue, I reported and blocked them. -Randy

Sure enough, in the .traefik/config directory there were two files ``` sma-dec24.yaml sma.yaml ``` The sma-dec24.yaml was from Feb 22. And it had this orphaned stuff in it: ``` http:...

> If anything at all could be changed, perhaps updating the docs for [How can I change a project’s name?](https://docs.ddev.com/en/stable/users/usage/faq/#how-can-i-change-a-projects-name) to mention clearing .ddev/traefik/ if there's issues starting up after...

@ayalon if you share your .ddev/traefik/config as a zipball or tarball, we're happy to help you study what's going on. The old behavior masked a number of weird problems, so...

The traefik running configuration is stored in the ddev-global-cache volume. The `ddev-router` is a shared resource between all projects, and it uses that config. If the config is broken, it...

* #7660 addresses this and now gives a warning in this situation.

Hi and welcome @josefglatz - * You didn't provide the requested `ddev debug test` output, could you please do that in a demo project? * You didn't explain how you...

Side note, the default `nodejs_version` for new projects will be `24` in upcoming DDEV v1.25.0.

Do the tests that fail work for you locally? (And running the ones that fail all together?)

This had nothing to do with docker upgrade/downgrade, right? It had to do with killing docker while ddev was running, then using `ddev start`, which picked up orphaned/dead containers?