# Sage 9 main.css 404 on devUrl

**URL:** https://discourse.roots.io/t/sage-9-main-css-404-on-devurl/9799
**Category:** sage
**Tags:** browsersync, webpack, sage9
**Created:** 2017-06-13T16:35:05Z
**Posts:** 38
**Showing post:** 34 of 38

## Post 34 by @ttamnedlog — 2017-10-10T16:09:35Z

The problem I experience with this is I have 2 browser tabs open when developing: 1) example.dev/wp-admin for backend WP business, and 2) localhost:3000 for seeing the frontend with my changing styles and content.

It’s lose-lose in the backend. Either I access the backend via localhost:3000 and receive errors such as the customizer not displaying the frontend because it violates a CSP that is expecting all URLs to originate from localhost:3000, or I access the backend via example.dev and am constantly presented with a red banner across the middle of the screen when editing a post/page that warns, “Failed to load content css: [https://example.dev/app/themes/example-theme/dist/styles/main.css](https://example.dev/app/themes/example-theme/dist/styles/main.css)”.

---

_[View the full topic](https://discourse.roots.io/t/sage-9-main-css-404-on-devurl/9799)._