After Magento 2.4.3 install css and js not loaded. In url 'pub' missing

After Magento 2.4.3 install css and js not loaded. In url 'pub' missing

August 30, 2026 · Illustrated author avatarBy Stefan Bogdanescu
After Magento 2.4.3 install css and js not loaded. In url 'pub' missing

Magento CSS and JS Not Loading After Install - The ‘pub’ Folder Issue

If you’re experiencing issues where your Magento frontend CSS and JavaScript are not loading after an installation or upgrade, you’re not alone. This is a common problem that can often be traced back to the ‘pub’ folder in your project’s root directory.

Understanding the Problem

When Magento processes requests for static files like CSS and JS, it looks for them within the ‘pub/static’ subdirectory of your project’s root. However, if the URLs generated by Magento are missing the ‘pub’ prefix, as you’ve noticed:

https://localhost/love/static/frontend/Infortis/ultimo/en_GB/css/print.min.css

instead of

https://localhost/love/pub/static/frontend/Infortis/ultimo/en_GB/css/print.min.css

your browser won’t be able to find the requested files, leading to the “Not Found” error you’re likely seeing.

The Culprit: Incorrect Static File Deployment

The most common cause of this issue is a failed or incomplete static file deployment. Magento’s static content deployment process (initiated by bin/magento setup:static-content:deploy) is responsible for copying these files from their source locations to the ‘pub/static’ folder where they can be served.

Debugging the Issue

To diagnose the problem further, let’s take a closer look at your project structure:

Checking Your Project Structure

Firstly, ensure that your project folder looks something like this:

your-project-folder/
├── app/
├── bin/
├── dev/
├── generated/
├── lib/
├── pub/
└── vendor/

Notice the ‘pub’ directory at the root level. If it’s missing or empty, you’ve found your issue.

Verifying the Static Content

Navigate to pub/static and check if your theme-specific folders are present:

your-project-folder/pub/static
├── frontend
│   └── Infortis
│       └── ultimo
└── ...

If they’re there but still empty after running bin/magento setup:static-content:deploy, the deployment step may have failed.

Resolving the Issue

Here are some steps you can take to troubleshoot and resolve this problem:

Step 1: Clear Cache and Generation Folders

Before proceeding with any further actions, make sure you clear your Magento cache and generation folders:

rm -rf var/cache/*
rm -rf var/generation/*

Step 2: Re-deploy Static Content

Run the static content deployment command again, this time specifying the desired scope:

  • For a default installation:

    bin/magento setup:static-content:deploy
    
  • If you’re using multiple themes or locales:

    bin/magento setup:static-content:deploy en_US fr_FR
    

Step 3: Check Output for Errors

Pay close attention to the output of this command. Any errors or warnings could indicate issues with your theme or third-party extensions.

If everything looks good, you should see a successful deployment message.

Troubleshooting Common Issues

Incorrect File Permissions

Ensure that the ‘pub’ folder and its subdirectories have the correct permissions for Magento to access them. The recommended permissions are:

  • pub: 755
  • pub/static: 775
  • pub/media & pub/static: 777

Missing Extensions or Dependencies

If you’ve installed third-party extensions or themes, make sure they don’t contain any conflicting configuration options that might interfere with the static file deployment process.

Composer and Magento Setup Issues

Sometimes, problems can arise due to issues with your Composer setup or during the initial Magento installation. Ensure you follow all steps correctly when setting up a new instance.

Conclusion: Ensuring Successful Static Content Deployment

In most cases, the solution lies in a proper static file deployment process. Always ensure that:

  • Your project has the correct directory structure.
  • You clear cache and generation folders before each deployment.
  • You run the setup:static-content:deploy command with the appropriate scope.
  • Your server configuration allows for successful file writing to the ‘pub’ folder.

If you’re still facing issues, double-check your configuration files (especially app/etc/env.php) for any potential errors or misconfigurations. Don’t hesitate to reach out to Magento’s documentation or support resources if needed.

Remember that proper static content deployment is a crucial aspect of maintaining a stable and performant Magento installation. By following these guidelines, you’ll minimize the risk of encountering issues like this in the future.

For more detailed information on Magento 2 setup best practices, I recommend visiting Laravel Company’s official blog for expert insights and tips.

Magento 2 Themes Deployment Errors

Our network