[GH-ISSUE #714] log_format in advanced tab not working

kerem commented

2026-02-26 06:33:37 +03:00

Owner

Originally created by @Treppengelaender on GitHub (Nov 11, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/714

I want to add a Custom Nginx Configuration to my Proxy Host.
I've added the command
access_log /path/to/logfile.log proxy;
with success.
But now i want to change the output of the logfile.
I thought it is as easy as declare a new log_format into the Custom Configuration Window.
But when i try to add something like
log_format custom '$remote_addr - $remote_user';
the Status from this Proxy Hosts toggles from Online to Offline.

Is there a good solution to customize the log_format? Is it just a bug and it shoult be in general possible to edit the log_format in the Custom Nginx Configuration Window?

Best Regards

Originally created by @Treppengelaender on GitHub (Nov 11, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/714 I want to add a Custom Nginx Configuration to my Proxy Host. I've added the command access_log /path/to/logfile.log proxy; with success. But now i want to change the output of the logfile. I thought it is as easy as declare a new log_format into the Custom Configuration Window. But when i try to add something like log_format custom '$remote_addr - $remote_user'; the Status from this Proxy Hosts toggles from Online to Offline. Is there a good solution to customize the log_format? Is it just a bug and it shoult be in general possible to edit the log_format in the Custom Nginx Configuration Window? Best Regards

kerem

2026-02-26 06:33:37 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@Highview-Lucas commented on GitHub (Nov 16, 2020):

the project sets it's own log file format for some reason.

It would be nice to have the option of selecting one of the standard (apache/nginx/etc) ones, or overriding it entirely.

@Highview-Lucas commented on GitHub (Nov 16, 2020): the project sets it's own log file format for some reason. It would be nice to have the option of selecting one of the standard (apache/nginx/etc) ones, or overriding it entirely.

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@wasn-eu commented on GitHub (Nov 17, 2020):

I go with that
To use the standard analyzer tools we need the standard log format

@wasn-eu commented on GitHub (Nov 17, 2020): I go with that To use the standard analyzer tools we need the standard log format

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@tuxmeister commented on GitHub (Nov 19, 2020):

I honestly can't find a good reason for this project to have a non-standard log format by default. I've been fighting with telegraf and grok patterns (new stuff to me) for the better part of the afternoon just to get some metrics into Influx... just... why? I can't even find the source place where this is defined to change it before the container is configured.

@jc21 would adding the custom output format in one of the "advanced config" file appenders work?

EDIT: just to clarify, I have not been successful with grok, even though I'm using a constructor to help me, I still find that for most of my proxy hosts, the cache status is a dash so I can't make one pattern to rule them all (within my ability and patience right now).

@tuxmeister commented on GitHub (Nov 19, 2020): I honestly can't find a good reason for this project to have a non-standard log format by default. I've been fighting with telegraf and grok patterns (new stuff to me) for the better part of the afternoon just to get some metrics into Influx... just... why? I can't even find the source place where this is defined to change it before the container is configured. @jc21 would adding the custom output format in one of the "advanced config" file appenders work? EDIT: just to clarify, I have not been successful with grok, even though I'm using a constructor to help me, I still find that for most of my proxy hosts, the cache status is a dash so I can't make one pattern to rule them all (within my ability and patience right now).

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@Highview-Lucas commented on GitHub (Nov 20, 2020):

the log_format definitions need to go into the base nginx.conf, the actual logging line can just go into the host definition. (so you can't just put it into the custom configuration inside the webUI, as you've discovered)

/etc/nginx/nginx.conf inside the docker container has log_format entries on lines 46/47

You can comment out these two lines and put in standard ("combined") log_format definitions - i don't have them handy, I'm at work, nginx docs should have the standard ones though!

make sure you name them correctly, the lines will need to start with "log_format proxy" and "log_format standard"

this does leave us an opening to define log_formats and then select which one we want per host inside the WebUI (and by "we" i mean someone else ;) )

@Highview-Lucas commented on GitHub (Nov 20, 2020): the log_format definitions need to go into the base nginx.conf, the actual logging line can just go into the host definition. (so you can't just put it into the custom configuration inside the webUI, as you've discovered) /etc/nginx/nginx.conf inside the docker container has log_format entries on lines 46/47 You can comment out these two lines and put in standard ("combined") log_format definitions - i don't have them handy, I'm at work, nginx docs should have the standard ones though! make sure you name them correctly, the lines will need to start with "log_format proxy" and "log_format standard" this does leave us an opening to define log_formats and then select which one we want per host inside the WebUI (and by "we" i mean someone else ;) )

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@Treppengelaender commented on GitHub (Nov 20, 2020):

Yes, editing /etc/nginx/nginx.conf works. It is also possible to add a line log_format customtemplate 'YOUROPTIONSHERE';
But wouldn't updating the container destroy changes made in /etc/nginx/nginx.conf?
Is there a way to change the log_format or set a custom log_format in the /data directory in the container?

@Treppengelaender commented on GitHub (Nov 20, 2020): Yes, editing /etc/nginx/nginx.conf works. It is also possible to add a line log_format customtemplate 'YOUROPTIONSHERE'; But wouldn't updating the container destroy changes made in /etc/nginx/nginx.conf? Is there a way to change the log_format or set a custom log_format in the /data directory in the container?

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@Highview-Lucas commented on GitHub (Nov 26, 2020):

I think I ended up putting /etc/nginx into a bind-mounted directory - changes persist through recreations - but if there's a huge change, it's likely to bite me.

@Highview-Lucas commented on GitHub (Nov 26, 2020): I think I ended up putting /etc/nginx into a bind-mounted directory - changes persist through recreations - but if there's a huge change, it's likely to bite me.

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@d33pjs commented on GitHub (May 1, 2021):

Upvote this feature. Did anyone got that working with advanced configurations?

@d33pjs commented on GitHub (May 1, 2021): Upvote this feature. Did anyone got that working with advanced configurations?

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@chaptergy commented on GitHub (May 12, 2021):

You could open a PR with this change (removing the log_format from nginx.conf) and explaining your reasons. Removing the two lines is not much effort. The worst thing that could happen is that he rejects it and you have wasted 5 minutes of your time.

@chaptergy commented on GitHub (May 12, 2021): You could open a PR with this change (removing the `log_format` from `nginx.conf`) and explaining your reasons. Removing the two lines is not much effort. The worst thing that could happen is that he rejects it and you have wasted 5 minutes of your time.

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@PathToLife commented on GitHub (Jun 2, 2021):

You can specify a custom log_format by creating a file in

/data/nginx/custom/http_top.conf

then restarting the server.

whatever is inside there is injected directly into http {} of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf

example below i added real-ip [Real-ip $http_cf_connecting_ip]

log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"';

then added in the dashboard access_log /data/logs/proxy2_host-7.log proxy2;

note log_format standard log_format proxy are already defined nginx does not let you override them

@PathToLife commented on GitHub (Jun 2, 2021): You can specify a custom log_format by creating a file in `/data/nginx/custom/http_top.conf` then restarting the server. whatever is inside there is injected directly into `http {}` of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf example below i added real-ip `[Real-ip $http_cf_connecting_ip]` ``` log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"'; ``` then added in the dashboard `access_log /data/logs/proxy2_host-7.log proxy2;` ![image](https://user-images.githubusercontent.com/12622625/120562187-04b4f180-c45a-11eb-8912-a2d0ab1826fb.png) note `log_format standard` `log_format proxy` are already defined *nginx does not let you override them*

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@d33pjs commented on GitHub (Jun 4, 2021):

You can specify a custom log_format by creating a file in

/data/nginx/custom/http_top.conf

then restarting the server.

whatever is inside there is injected directly into http {} of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf

example below i added real-ip [Real-ip $http_cf_connecting_ip]
log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"';
then added in the dashboard access_log /data/logs/proxy2_host-7.log proxy2;

note log_format standard log_format proxy are already defined nginx does not let you override them

This worked perfectly. Thank you so much!

@d33pjs commented on GitHub (Jun 4, 2021): > You can specify a custom log_format by creating a file in > > `/data/nginx/custom/http_top.conf` > > then restarting the server. > > whatever is inside there is injected directly into `http {}` of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf > > example below i added real-ip `[Real-ip $http_cf_connecting_ip]` > > ``` > log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"'; > ``` > > then added in the dashboard `access_log /data/logs/proxy2_host-7.log proxy2;` > > ![image](https://user-images.githubusercontent.com/12622625/120562187-04b4f180-c45a-11eb-8912-a2d0ab1826fb.png) > > note `log_format standard` `log_format proxy` are already defined _nginx does not let you override them_ This worked perfectly. Thank you so much!

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@AMWN commented on GitHub (Oct 25, 2021):

I go with that To use the standard analyzer tools we need the standard log format

Made a regexp for the custom proxy log_format. It's not perfect, but works for me for scraping with Promtail.

\[(?P<dateandtime>\d{2}\/[A-z]{3}\/\d{4}:\d{2}:\d{2}:\d{2} (\+|\-)\d{4})\] (?P<upstream_cache_status>-) (?P<upstream_status>[^ ]*) (?P<status>[^ ]*) - (?P<request_method>[\w\.]+) (?P<scheme>[\w\.]+) (?P<host>[^"]*) "(?P<request_uri>[^"]*)" \[Client (?P<remote_addr>[\w\.]+)\] \[Length (?P<bytessent>\d+)\] \[Gzip (?P<gzip_ratio>[^ ])\] \[Sent-to (?P<Sentto>[^"]*)\] "(?P<http_user_agent>[^"]*)" "(?P<http_referer>[^"]*)"

@AMWN commented on GitHub (Oct 25, 2021): > I go with that To use the standard analyzer tools we need the standard log format Made a regexp for the custom proxy log_format. It's not perfect, but works for me for scraping with Promtail. `\[(?P<dateandtime>\d{2}\/[A-z]{3}\/\d{4}:\d{2}:\d{2}:\d{2} (\+|\-)\d{4})\] (?P<upstream_cache_status>-) (?P<upstream_status>[^ ]*) (?P<status>[^ ]*) - (?P<request_method>[\w\.]+) (?P<scheme>[\w\.]+) (?P<host>[^"]*) "(?P<request_uri>[^"]*)" \[Client (?P<remote_addr>[\w\.]+)\] \[Length (?P<bytessent>\d+)\] \[Gzip (?P<gzip_ratio>[^ ])\] \[Sent-to (?P<Sentto>[^"]*)\] "(?P<http_user_agent>[^"]*)" "(?P<http_referer>[^"]*)"`

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@TehloWasTaken commented on GitHub (Mar 3, 2022):

You can specify a custom log_format by creating a file in

/data/nginx/custom/http_top.conf

then restarting the server.

whatever is inside there is injected directly into http {} of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf

example below i added real-ip [Real-ip $http_cf_connecting_ip]
log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"';
then added in the dashboard access_log /data/logs/proxy2_host-7.log proxy2;

note log_format standard log_format proxy are already defined nginx does not let you override them

Hey, thanks for posting this. I just tried doing this but it isn't working properly and it isn't reading my config file to apply the custom log format. Could you maybe help me out?

I am trying to use the log format from this link:
https://grafana.com/grafana/dashboards/12559

I applied it in the http_top.conf in the proper folder, but it just isn't reading it and still applying the standard format. Help?

@TehloWasTaken commented on GitHub (Mar 3, 2022): > You can specify a custom log_format by creating a file in > > `/data/nginx/custom/http_top.conf` > > then restarting the server. > > whatever is inside there is injected directly into `http {}` of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf > > example below i added real-ip `[Real-ip $http_cf_connecting_ip]` > > ``` > log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"'; > ``` > > then added in the dashboard `access_log /data/logs/proxy2_host-7.log proxy2;` > > ![image](https://user-images.githubusercontent.com/12622625/120562187-04b4f180-c45a-11eb-8912-a2d0ab1826fb.png) > > note `log_format standard` `log_format proxy` are already defined _nginx does not let you override them_ Hey, thanks for posting this. I just tried doing this but it isn't working properly and it isn't reading my config file to apply the custom log format. Could you maybe help me out? I am trying to use the log format from this link: https://grafana.com/grafana/dashboards/12559 I applied it in the http_top.conf in the proper folder, but it just isn't reading it and still applying the standard format. Help?

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@motionrus commented on GitHub (Jan 12, 2023):

You can specify a custom log_format by creating a file in

/data/nginx/custom/http_top.conf

then restarting the server.

whatever is inside there is injected directly into http {} of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf

example below i added real-ip [Real-ip $http_cf_connecting_ip]
log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"';
then added in the dashboard access_log /data/logs/proxy2_host-7.log proxy2;

note log_format standard log_format proxy are already defined nginx does not let you override them

My data/nginx/proxy_host/1.conf file now duplicates the logs

  access_log /data/logs/proxy-host-1_access.log proxy;
  error_log /data/logs/proxy-host-1_error.log warn;
  access_log /data/logs/proxy-host-1_access.log upstream_time ;

If I look at the proxy-host-1_access.log file, I see duplication

==> data/logs/proxy-host-1_access.log <==
[12/Jan/2023:05:24:15 +0000] - 304 304 - GET https motionrus.site "/" [Client 77.51.203.17] [Length 0] [Gzip -] [Sent-to 172.31.21.178] "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36" "-"
77.51.203.17 - - [12/Jan/2023:05:24:15 +0000] "GET / HTTP/2.0" 304 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36"rt=0.001 uct="0.000" uht="0.004" urt="0.004"

Here is my data/nginx/custom/http_top.conf

    log_format upstream_time '$remote_addr - $remote_user [$time_local] '
                             '"$request" $status $body_bytes_sent '
                             '"$http_referer" "$http_user_agent"'
                             'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"';

Does anyone know how to solve the problem with duplication?

@motionrus commented on GitHub (Jan 12, 2023): > You can specify a custom log_format by creating a file in > > `/data/nginx/custom/http_top.conf` > > then restarting the server. > > whatever is inside there is injected directly into `http {}` of nginx.conf https://github.com/jc21/nginx-proxy-manager/blob/master/docker/rootfs/etc/nginx/nginx.conf > > example below i added real-ip `[Real-ip $http_cf_connecting_ip]` > > ``` > log_format proxy2 '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Real-ip $http_cf_connecting_ip] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"'; > ``` > > then added in the dashboard `access_log /data/logs/proxy2_host-7.log proxy2;` > > ![image](https://user-images.githubusercontent.com/12622625/120562187-04b4f180-c45a-11eb-8912-a2d0ab1826fb.png) > > note `log_format standard` `log_format proxy` are already defined _nginx does not let you override them_ My `data/nginx/proxy_host/1.conf` file now duplicates the logs ``` access_log /data/logs/proxy-host-1_access.log proxy; error_log /data/logs/proxy-host-1_error.log warn; access_log /data/logs/proxy-host-1_access.log upstream_time ; ``` If I look at the `proxy-host-1_access.log` file, I see duplication ``` ==> data/logs/proxy-host-1_access.log <== [12/Jan/2023:05:24:15 +0000] - 304 304 - GET https motionrus.site "/" [Client 77.51.203.17] [Length 0] [Gzip -] [Sent-to 172.31.21.178] "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36" "-" 77.51.203.17 - - [12/Jan/2023:05:24:15 +0000] "GET / HTTP/2.0" 304 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36"rt=0.001 uct="0.000" uht="0.004" urt="0.004" ``` Here is my `data/nginx/custom/http_top.conf` ``` log_format upstream_time '$remote_addr - $remote_user [$time_local] ' '"$request" $status $body_bytes_sent ' '"$http_referer" "$http_user_agent"' 'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"'; ``` Does anyone know how to solve the problem with duplication?

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@okworx commented on GitHub (Jan 21, 2023):

Made a regexp for the custom proxy log_format. It's not perfect, but works for me for scraping with Promtail.

\[(?P<dateandtime>\d{2}\/[A-z]{3}\/\d{4}:\d{2}:\d{2}:\d{2} (\+|\-)\d{4})\] (?P<upstream_cache_status>-) (?P<upstream_status>[^ ]*) (?P<status>[^ ]*) - (?P<request_method>[\w\.]+) (?P<scheme>[\w\.]+) (?P<host>[^"]*) "(?P<request_uri>[^"]*)" \[Client (?P<remote_addr>[\w\.]+)\] \[Length (?P<bytessent>\d+)\] \[Gzip (?P<gzip_ratio>[^ ])\] \[Sent-to (?P<Sentto>[^"]*)\] "(?P<http_user_agent>[^"]*)" "(?P<http_referer>[^"]*)"

Here's a regex that works for import into Matomo together with --log-date-format='%d/%b/%Y:%H:%M:%S %z':

'\[(?P<date>\d{2}\/[A-z]{3}\/\d{4}:\d{2}:\d{2}:\d{2}\s+(\+|\-)\d{4})\]\s+(?P<upstream_cache_status>-)\s+(?P<upstream_status>[^ ]*)\s+(?P<status>[^ ]*)\s+-\s+(?P<request_method>[\w\.]+)\s+(?P<scheme>[\w\.]+)\s+(?P<host>[^"]*)\s+"(?P<path>[^"]*)"\s+\[Client (?P<ip>[\w\.]+)\]\s+\[Length (?P<bytessent>\d+)\]\s+\[Gzip\s+(?P<gzip_ratio>[\d\.\-]+)\]\s+\[Sent-to (?P<Sentto>[^"]*)\]\s+"(?P<user_agent>[^"]*)"\s+"(?P<referrer>[^"]*)"'

@okworx commented on GitHub (Jan 21, 2023): > Made a regexp for the custom proxy log_format. It's not perfect, but works for me for scraping with Promtail. > > `\[(?P<dateandtime>\d{2}\/[A-z]{3}\/\d{4}:\d{2}:\d{2}:\d{2} (\+|\-)\d{4})\] (?P<upstream_cache_status>-) (?P<upstream_status>[^ ]*) (?P<status>[^ ]*) - (?P<request_method>[\w\.]+) (?P<scheme>[\w\.]+) (?P<host>[^"]*) "(?P<request_uri>[^"]*)" \[Client (?P<remote_addr>[\w\.]+)\] \[Length (?P<bytessent>\d+)\] \[Gzip (?P<gzip_ratio>[^ ])\] \[Sent-to (?P<Sentto>[^"]*)\] "(?P<http_user_agent>[^"]*)" "(?P<http_referer>[^"]*)"` Here's a regex that works for import into Matomo together with `--log-date-format='%d/%b/%Y:%H:%M:%S %z'`: `'\[(?P<date>\d{2}\/[A-z]{3}\/\d{4}:\d{2}:\d{2}:\d{2}\s+(\+|\-)\d{4})\]\s+(?P<upstream_cache_status>-)\s+(?P<upstream_status>[^ ]*)\s+(?P<status>[^ ]*)\s+-\s+(?P<request_method>[\w\.]+)\s+(?P<scheme>[\w\.]+)\s+(?P<host>[^"]*)\s+"(?P<path>[^"]*)"\s+\[Client (?P<ip>[\w\.]+)\]\s+\[Length (?P<bytessent>\d+)\]\s+\[Gzip\s+(?P<gzip_ratio>[\d\.\-]+)\]\s+\[Sent-to (?P<Sentto>[^"]*)\]\s+"(?P<user_agent>[^"]*)"\s+"(?P<referrer>[^"]*)"'`

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@hoseinmont commented on GitHub (Nov 15, 2023):

see this link.
work for me

@hoseinmont commented on GitHub (Nov 15, 2023): see [this link](https://zachthesplunker.com/splunk-the-nginx-proxy-manager/). work for me

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 19, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (May 19, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@Brendon-Mendicino commented on GitHub (Jun 16, 2024):

would it be possible to include the the log_format proxy from a different file in order to override it using some mounted file? This allows for an easier way of overriding the default format for each service.

writing our own custom log_format and then specifying it for each service is quite tedious.

@Brendon-Mendicino commented on GitHub (Jun 16, 2024): would it be possible to include the the `log_format proxy` from a different file in order to override it using some mounted file? This allows for an easier way of overriding the default format for each service. writing our own custom `log_format` and then specifying it for each service is quite tedious.

kerem commented

2026-02-26 06:33:38 +03:00

Author

Owner

@ThatCoffeeGuy commented on GitHub (Aug 2, 2024):

This could integrate so well with GoAccess on default, but this questionable design choice makes it a headache to set it up. Please reconsider changing it back to the default logging format.

@ThatCoffeeGuy commented on GitHub (Aug 2, 2024): This could integrate so well with GoAccess on default, but this questionable design choice makes it a headache to set it up. Please reconsider changing it back to the default logging format.

Rows
Columns

[GH-ISSUE #714] log_format in advanced tab not working #605