[GH-ISSUE #1285] IP Address missing in audit log #361

Closed
opened 2026-02-26 18:46:41 +03:00 by kerem · 1 comment
Owner

Originally created by @Rainson12 on GitHub (Aug 13, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1285

Issue Description

When signing a document the IP Address field is empty in the audit log.

Steps to Reproduce

Run Documenso in a docker container, create a reverse proxy to forward traffic into docker container. Send out a document for singing and after signing no IP addresses are shown in the audit log (maybe due to the reverse proxies?

Expected Behavior

IP Address would be properly shown

Current Behavior

IP Address is empty

Screenshots (optional)

image

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Chrome

Version [e.g., 2.0.1]

1.6.1

Please check the boxes that apply to this issue report.

  • I have searched the existing issues to make sure this is not a duplicate.
  • I have provided steps to reproduce the issue.
  • I have included relevant environment information.
  • I have included any relevant screenshots.
  • I understand that this is a voluntary contribution and that there is no guarantee of resolution.
  • I want to work on creating a PR for this issue if approved
Originally created by @Rainson12 on GitHub (Aug 13, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1285 ### Issue Description When signing a document the IP Address field is empty in the audit log. ### Steps to Reproduce Run Documenso in a docker container, create a reverse proxy to forward traffic into docker container. Send out a document for singing and after signing no IP addresses are shown in the audit log (maybe due to the reverse proxies? ### Expected Behavior IP Address would be properly shown ### Current Behavior IP Address is empty ### Screenshots (optional) ![image](https://github.com/user-attachments/assets/cc1ececb-7d4e-4878-be8f-6c16771bd1ae) ### Operating System [e.g., Windows 10] Windows 11 ### Browser [e.g., Chrome, Firefox] Chrome ### Version [e.g., 2.0.1] 1.6.1 ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [X] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [X] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved
kerem 2026-02-26 18:46:41 +03:00
Author
Owner

@Rainson12 commented on GitHub (Aug 13, 2024):

I figured when chaining a reverse proxy IIS -> NGINX -> Docker container the x-forwarded-for is incorrect when using $proxy_add_x_forwarded_for. I am now using $http_x_forwarded_for instead and it works fine.

<!-- gh-comment-id:2285921154 --> @Rainson12 commented on GitHub (Aug 13, 2024): I figured when chaining a reverse proxy IIS -> NGINX -> Docker container the x-forwarded-for is incorrect when using `$proxy_add_x_forwarded_for`. I am now using `$http_x_forwarded_for` instead and it works fine.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#361
No description provided.