Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

lukeboy_2002's avatar

After deploy with filament net::ERR_NAME_NOT_RESOLVED

Hi,

I want to use filament for my admin section. After I deployed my site I get the error when loading a image in my filament admin section net::ERR_NAME_NOT_RESOLVED.

On the front-page there is no problem and the images are loaded. When I make a new item with a filament form there is also no error on the front-page.

My public, website, is in another directory than my laravel. I made changes in my index in the public that points to the laravel directory. My Site is hosted at Strato. I made a subdomain that points to my public. Public: public_filament

changed in index

if (file_exists($maintenance = DIR.'/../filament/storage/framework/maintenance.php')) { require $maintenance; }

require DIR.'/../filament/vendor/autoload.php $app = require_once DIR.'/../filament/bootstrap/app.php';

When I look to both images it gives in my inspector the same directory.

Can someone help me?

0 likes
1 reply
LaryAI's avatar
Level 58

This error typically occurs when the domain name cannot be resolved to an IP address. Here are a few steps you can take to troubleshoot and resolve the issue:

  1. Check DNS Configuration: Ensure that the domain name is correctly configured in your DNS settings. Double-check the A record and make sure it points to the correct IP address.

  2. Clear DNS Cache: Clear your local DNS cache to ensure that you are not using outdated DNS information. You can do this by running the following command in your terminal or command prompt:

    ipconfig /flushdns
    
  3. Check Firewall Settings: Make sure that your server's firewall is not blocking the connection to the domain. Check both the server's firewall settings and any network firewalls that may be in place.

  4. Test with IP Address: Instead of using the domain name, try accessing the image using the IP address directly. If the image loads successfully, it indicates that there might be an issue with the DNS configuration.

  5. Check File Permissions: Ensure that the image files have the correct permissions set. They should be readable by the web server user.

  6. Verify File Paths: Double-check that the file paths in your code are correct. If the images are stored in a different directory, make sure the paths are updated accordingly.

If none of the above steps resolve the issue, it might be helpful to provide more information about your server setup, including the web server you are using and any relevant configuration files.

Please or to participate in this conversation.