NGINX Proxy Manager LXC - geoip2 module missing #160

Closed
opened 2026-02-04 16:53:28 +03:00 by OVERLORD · 7 comments
Owner

Originally created by @lepo80 on GitHub (Dec 10, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

I don't find the geoip2 module presence. I tried to install after the current script installation, but when upgrade the container the geoip2 modle broken.

is it feasable to add it into the current NGINX Proxy Manager LXC script intallation, please?
thanks

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

the geoip2 module is missing into the current script installation

Please provide detailed steps to reproduce the issue.

N/A

Originally created by @lepo80 on GitHub (Dec 10, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. I don't find the geoip2 module presence. I tried to install after the current script installation, but when upgrade the container the geoip2 modle broken. is it feasable to add it into the current NGINX Proxy Manager LXC script intallation, please? thanks ### What settings are you currently utilizing? - [X] Default Settings - [X] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. the geoip2 module is missing into the current script installation ### Please provide detailed steps to reproduce the issue. N/A
OVERLORD added the question label 2026-02-04 16:53:28 +03:00
Author
Owner

@MickLesk commented on GitHub (Dec 10, 2024):

what are you talking about? I looked at the installation and found no problems. What is your problem? Without logs and a detailed description, I can only ask the crystal ball, but it often lies.

Or are you talking about the same problem as the other issue? There is an active PR fix.

@MickLesk commented on GitHub (Dec 10, 2024): what are you talking about? I looked at the installation and found no problems. What is your problem? Without logs and a detailed description, I can only ask the crystal ball, but it often lies. Or are you talking about the same problem as the other issue? There is an active PR fix.
Author
Owner

@lepo80 commented on GitHub (Dec 10, 2024):

The current installation doesn't have the geoip2 module installed. Did you find it?
My simply request is to add it into the current installation script, of it is feasible... I tried to add it in secondary step, but when I upgrade the lxc using the script, the geoip module it doesn't work anymore.
Frankly speaking, I don't get your message meaning. If my request is out of the issue request expectations, it can be deleted.
For myself, the geoip2 module can very useful into the reverse proxy service.

@lepo80 commented on GitHub (Dec 10, 2024): The current installation doesn't have the geoip2 module installed. Did you find it? My simply request is to add it into the current installation script, of it is feasible... I tried to add it in secondary step, but when I upgrade the lxc using the script, the geoip module it doesn't work anymore. Frankly speaking, I don't get your message meaning. If my request is out of the issue request expectations, it can be deleted. For myself, the geoip2 module can very useful into the reverse proxy service.
Author
Owner

@MickLesk commented on GitHub (Dec 10, 2024):

What is geoip2? Its Not a dependency

@MickLesk commented on GitHub (Dec 10, 2024): What is geoip2? Its Not a dependency
Author
Owner

@lepo80 commented on GitHub (Dec 10, 2024):

The GeoIP2 module for NGINX is an advanced feature used to determine the geographical location of users accessing your server. It integrates with MaxMind's GeoIP2 databases to map IP addresses to specific data, such as country, city, latitude, longitude, ISP, and more. This information can be utilized to tailor content, apply location-based restrictions, or enhance logging and analytics. The module requires the GeoIP2 library and databases to be installed separately and supports configuration through directives in the NGINX configuration file. It's a modern alternative to the older GeoIP module, offering better accuracy and more detailed data.

For example, you have a lab environment and you want to accept the connection to your site/service provided by NGINX for only a specific country /region (security needs). This module permits to declare it into the Nginx host advanced configuration.

@lepo80 commented on GitHub (Dec 10, 2024): The GeoIP2 module for NGINX is an advanced feature used to determine the geographical location of users accessing your server. It integrates with MaxMind's GeoIP2 databases to map IP addresses to specific data, such as country, city, latitude, longitude, ISP, and more. This information can be utilized to tailor content, apply location-based restrictions, or enhance logging and analytics. The module requires the GeoIP2 library and databases to be installed separately and supports configuration through directives in the NGINX configuration file. It's a modern alternative to the older GeoIP module, offering better accuracy and more detailed data. For example, you have a lab environment and you want to accept the connection to your site/service provided by NGINX for only a specific country /region (security needs). This module permits to declare it into the Nginx host advanced configuration.
Author
Owner

@lepo80 commented on GitHub (Dec 10, 2024):

It be that I'm wrong to open a request like issue.. sorry for this!

@lepo80 commented on GitHub (Dec 10, 2024): It be that I'm wrong to open a request like issue.. sorry for this!
Author
Owner

@MickLesk commented on GitHub (Dec 10, 2024):

Then is this a topic for discussion, Not an issue.

@MickLesk commented on GitHub (Dec 10, 2024): Then is this a topic for discussion, Not an issue.
Author
Owner

@lepo80 commented on GitHub (Dec 10, 2024):

According to suggestion, I've opened a new discussion.

@lepo80 commented on GitHub (Dec 10, 2024): According to suggestion, I've opened a new discussion.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#160