Experiencing 404 Errors When Using Nginx as Reverse Proxy for imgproxy #20
-
|
Hi, I'm experiencing a 404 error when trying to load images through Nginx as a reverse proxy for imgproxy. Here are two example URLs where the error occurs: I've tried the suggested modification of adding Here are some of the errors I'm seeing: Interestingly, if I query imgproxy directly (bypassing Nginx), the images load correctly without any issues. Additionally, I noticed that if I comment out the following lines in my Nginx configuration, the images start working: docker-imgproxy/nginx/nginx.conf Lines 201 to 202 in 6f30ca6 I've also updated the Nginx configuration as follows, which seems to make it work: docker-imgproxy/nginx/nginx.conf Lines 242 to 245 in 6f30ca6 It seems like these lines are causing the issue, but I'm not entirely sure why. Any insights or suggestions would be greatly appreciated. Thanks for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Hello @skinner12, After reviewing the URLs from the log you posted, I noticed that something seems off with the URLs being passed to Could you show me your settings for the block |
Beta Was this translation helpful? Give feedback.
-
|
Hello @shinsenter , As I wrote before, the actual URL I access is: I took This one is coming from Also, I didn't modify anything, it's a fresh install. I just install your docker compose, I modified some imgproxy env's variables and nothing else. Just to be clear as more as possible, links with presets like I tried, also, to run it on my local machine but I have the same problem: |
Beta Was this translation helpful? Give feedback.
-
|
Hello @skinner12, thank you for your feedback. It seems that the way this setup is configured doesn't align with your intended usage. If you want to use the parameters directly in the URL following imgproxy's syntax, then this setup may not work as intended (instead, you might want to directly use it for a container that only runs imgproxy). My setup aims to create predefined presets with user-friendly keywords (like With my setup, you can add definitions for presets sent to imgproxy using specific keywords (see the settings I've prepared), and I believe it will work well. For example: First, you need to add a definition for your origin server (for example, ## **`$origin_server`**
## Define origin base URL from the request.
## This setup assumes that an origin server starts with an `@` symbol (such as `@nasa`, `@pinterest`, etc.).
## You can also add your own origin servers using [regular expressions](https://www.nginx.com/blog/regular-expression-tester-nginx/).
map $uri $origin_server
{
default 'local://';
# Put your rewrite rules for origin servers from here.
~^/@abc/ 'https://images.pexels.com/photos';
}Next, you can use or adjust the parameters for the presets I have prepared below: Lines 164 to 182 in 6f30ca6 Alternatively, you can add your own Then, you can access the image using the following path:
That's how my setup is designed to be used. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @shinsenter, Do you think that we need to setup a signature for every image or with your project we can avoid it? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the compliment. Since I also prefer to avoid complex parameters and the need to create signatures for simple HTML websites, I created this setup. I think this is just a basic setup for you to customize according to your specific requirements. Additionally, with this setup, you have defined quite specific image patterns that you will use, and frequently accessed images are cached by Nginx, which helps reduce processing for the imgproxy container. However, I also acknowledge that it doesn’t provide 100% protection against the malicious intentions of attackers. |
Beta Was this translation helpful? Give feedback.
-
|
@shinsenter I understand your point of view and you're right to keep it simple: also you can't add every single feature but your script seems modular and we can add more functions needed. I'll try to add by myself and check if it's worth use it. Thanks again |
Beta Was this translation helpful? Give feedback.
Hello @skinner12, thank you for your feedback.
It seems that the way this setup is configured doesn't align with your intended usage.
If you want to use the parameters directly in the URL following imgproxy's syntax, then this setup may not work as intended (instead, you might want to directly use it for a container that only runs imgproxy).
My setup aims to create predefined presets with user-friendly keywords (like
_thumbnail,_medium,_blurry, etc.) to mask the parameters that call imgproxy, making the URL more user-friendly and preventing attacks by injecting unnecessary parameters into the imgproxy container.With my setup, you can add definitions for presets sent to imgproxy using s…