Body: <p>Basically, I have an asset volume called Images, with </p>
  
  <p>base URL: /photos/
  file system path: ~media/images</p>
  
  <p>Then I go to upload the asset and I try to view it, it gives me a 404 "Template not Found"</p>
  
  <p>mydomain.com/photos/image.jpg</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-23T02:25:46.263Z
Comments.Text: `~media/images` is going to point the user's home directory on *nix operating systems.  Maybe you meant to use a relative path? i.e. `media/images` or `./media/images`?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-23T14:55:56.110Z
Comments.Text: @BradBell thanks for your response.
  
  The files are there (in the right location).  I want to move them to another location eventually, but for now I just wanted to test and see if I could even access the assets publicly via URL.
  
  It shouldn't be giving a template error if it's correctly routing the URL to the file, right?
Comments.UserDisplayName: user3928094
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-12T00:34:12.943Z
Comments.Text: @BradBell I updated it to be a relative path and it is still giving me a templating error.
Comments.UserDisplayName: user3928094
Tags: <assets><craft3>
Title: Can't find assets publicly via URL
ThreadText: # Can't find assets publicly via URL
  
  (Asked by: username_0 on 2017-08-22)
  
  Basically, I have an asset volume called Images, with
  
  base URL: /photos/
  file system path: ~media/images
  
  Then I go to upload the asset and I try to view it, it gives me a 404 "Template not Found"
  
  mydomain.com/photos/image.jpg
  
  **Tags:** assets, craft3
  
  > **Comments:**
  > **username_1**: `~media/images` is going to point the user's home directory on *nix operating systems.  Maybe you meant to use a relative path? i.e. `media/images` or `./media/images`?  
  > **username_0**: @username_1 thanks for your response.  The files are there (in the right location).  I want to move them to another location eventually, but for now I just wanted to test and see if I could even access the assets publicly via URL.  It shouldn't be giving a template error if it's correctly routing the URL to the file, right?  
  > **username_0**: @username_1 I updated it to be a relative path and it is still giving me a templating error.  
  
  ---
  
  ## 0 answers
  
  