[GH-ISSUE #2881] FRP redirects me from the domain to 127.0.0.1:8080

gitea-mirror commented

2026-05-05 13:28:56 -06:00

Owner

Originally created by @Nuckerr on GitHub (Mar 31, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2881

Bug Description

When I go to nucker.me it redirects me to 127.0.0.1:8080 and I have no clue why. I have multiple other services working on this, the only difference is they use subdomains.

frpc Version

0.39.1

frps Version

0.39.1

System Architecture

linux/amd64

Configurations

[common]
token = [redacted]
server_addr = [redacted].nucker.me
server_port = 7000

admin_addr = 0.0.0.0
admin_port = 7400
admin_user = adminuser
admin_pwd = [redacted]
enable_prometheus = true

[blog]
type = https
custom_domains = nucker.me
plugin = https2http
plugin_local_addr = 192.168.0.139:8080
plugin_crt_path = /etc/certs/cert.pem
plugin_key_path = /etc/certs/key.pem
plugin_host_header_rewrite = 127.0.0.11
plugin_header_X-From-Where = frp

Logs

No response

Steps to reproduce

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @Nuckerr on GitHub (Mar 31, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2881 ### Bug Description When I go to `nucker.me` it redirects me to `127.0.0.1:8080` and I have no clue why. I have multiple other services working on this, the only difference is they use subdomains. ### frpc Version 0.39.1 ### frps Version 0.39.1 ### System Architecture linux/amd64 ### Configurations ```ini [common] token = [redacted] server_addr = [redacted].nucker.me server_port = 7000 admin_addr = 0.0.0.0 admin_port = 7400 admin_user = adminuser admin_pwd = [redacted] enable_prometheus = true [blog] type = https custom_domains = nucker.me plugin = https2http plugin_local_addr = 192.168.0.139:8080 plugin_crt_path = /etc/certs/cert.pem plugin_key_path = /etc/certs/key.pem plugin_host_header_rewrite = 127.0.0.11 plugin_header_X-From-Where = frp ``` ### Logs _No response_ ### Steps to reproduce _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror

2026-05-05 13:28:56 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:28:59 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 1, 2022):

Why you set plugin_host_header_rewrite = 127.0.0.11?

@fatedier commented on GitHub (Apr 1, 2022): Why you set `plugin_host_header_rewrite = 127.0.0.11`?

gitea-mirror commented

2026-05-05 13:29:01 -06:00

Author

Owner

@Nuckerr commented on GitHub (Apr 1, 2022):

Oh, it was originally 127.0.0.1 and then I tried to see if that was causing the redirect and changed it to 11. I've changed it back

@Nuckerr commented on GitHub (Apr 1, 2022): Oh, it was originally 127.0.0.1 and then I tried to see if that was causing the redirect and changed it to 11. I've changed it back

gitea-mirror commented

2026-05-05 13:29:02 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 1, 2022):

I'm not sure why you add this parameter. Try to remove it and see if it's ok.

@fatedier commented on GitHub (Apr 1, 2022): I'm not sure why you add this parameter. Try to remove it and see if it's ok.

gitea-mirror commented

2026-05-05 13:29:03 -06:00

Author

Owner

@Nuckerr commented on GitHub (Apr 1, 2022):

Now it redirects to nucker.me:8080

@Nuckerr commented on GitHub (Apr 1, 2022): Now it redirects to `nucker.me:8080`

gitea-mirror commented

2026-05-05 13:29:03 -06:00

Author

Owner

@Nuckerr commented on GitHub (Apr 5, 2022):

Any ideas?

@Nuckerr commented on GitHub (Apr 5, 2022): Any ideas?

gitea-mirror commented

2026-05-05 13:29:04 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (May 6, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (May 6, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.