Hi, There is a lot of errors in /logs, which states there is invalid input for update_ip_address operation. [image] The discourse is deployed in Azure, with a separated PostgreSQL and Redis service. Error logs: /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/patc…

[Bild] SimonWu: If your nginx setting is using $proxy_add_x_forwarded_for as the indicate of user ip. I think ip with port will be a valid input here. You may need to strip the port info out. Well, this needs to be amended upstream then, see: lib/rack/request.rb main …

[Bild] SimonWu: The discourse is deployed in Azure, with a separated PostgreSQL and Redis service. looks to me like you are forwarding an incorrect field to ip address. How do you have IP Address forwarding configured?

Thank you Sam. I didn’t configure that on purpose. Where can I check the config?

In the Azure setup… somewhere. That data is not coming from within Discourse.

It’s ip address from our company proxy. I don’t know how is the portal address added. Can we just remove the port info to accept this ip?

No, it isn’t an IP address, and that’s the problem. If you’ve got a proxy that’s including a port number in what’s supposed to be an IP address, then the proxy is broken, and you’ll want to get that fixed.

I haven’t find the root cause yet. But I find a defected solution. By adding the following configuration in app.yml. I make the input of ip_address valid. filename: /etc/nginx/conf.d/discourse.conf from: $proxy_add_x_forwarded_for to: $http_your_original_ip_header global…

According to RFC 7239 - Forwarded HTTP Extension 5.2. Forwarded For The “for” parameter is used to disclose information about the client that initiated the request and subsequent proxies in a chain of proxies. When proxies choose to use the “for” parameter, its default configuration SHOULD c…

That RFC describes the format of the Forwarded: HTTP request header. The X-Forwarded-For header, which we’re examining, has different semantics.

[Bild] sam: HTTP_X_FORWARDED_FOR Thanks for the correction. And for Azure Gateway, it does have a different definition for x-forwarded-for. See Frequently asked questions about Application Gateway | Microsoft Learn Q. Does Application Gateway support x-forwarded-for headers? Yes, Applica…

Hi, Just to add to the conversation - this is standard practice in Azure Application Gateways, and it’s infuriating. They add the port to the forwarded-for header even though they also send it in the forwarded port header. Two feedback/change requests on Microsoft which you can vote for; Page No…

Invalid input for update_ip_address

Unterstützung Installation

klopsknoedel (Sascha Hofmann) 18. September 2019 um 08:45 18

Eine kurze Ergänzung.
Die oben genannte „Lösung

Thema		Antworten	Aufrufe
Browser cookie corruption(?) after site migration on Azure Support	3	759	17. Februar 2020
Getting a 500 response when accessing Categories Index route Support	3	435	25. September 2019
Discourse shows server IP/localhost as user's IP Self-hosting unsupported-install	18	2310	12. Juli 2022
Commit b4a3389 更新后如何获取用户ip Self-hosting nginx , cloudflare	3	266	29. Juni 2026
All users have the same IP (the Servers IP)? Self-hosting	13	4291	28. Juli 2018

Invalid input for update_ip_address

Verwandte Themen