Hello, I have migrated a Discourse platform from Vultur host to Azure, within a CentOS linux flavour. The migration went smoothly, using the built in database backup and restore process. We then delegated the DNS. Some users (including myself at one point) are getting the sad face 500 error loading /latest.json. In all instances, clearing your cookies/sessions fixes the problem.. but it appears to come back after half an hour or so. I was also as an admin able to see during the error in my Settings section that the key-value pairs for the various settings labels were not parsed to a language locale e.g. “default locale” was displayed as something like “[en.default_locale]”. I am not a Linux or Discourse guru so have no idea where to go with this issue. It may be things “settling down” after DNS migration, or there could be something more going on. The problem so far has only been reported on Windows Chrome. I cannot reproduce on Edge or Chrome Android. Looking in the /logs I see entries such as the following: Job exception: PG::InvalidTextRepresentation: ERROR: invalid input syntax for type inet:"106.70.36.109:6082" LINE 1: UPDATE "users" SET "ip_address" = '106.70.36.109:6082' WHERE... Any advice would be appreciated. Simon

[image] Simon_Miller: invalid input syntax for type inet:“106.70.36.109:6082” That is a well know Azure bug with some workarounds described here [image] Invalid input for update_ip_address Self-hosting 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; Azure Application Gateway x-forwarded-for remove port information – Customer Feedback for Microsoft Azure Support for dropping port out of x-forwarded-for header – Customer Feedback for Microsoft Azure Our …

[image] Simon_Miller: I cannot reproduce on Edge Chromium Edge or Legacy Edge?

We came to this conclusion as well, and it was the case. The Appgw was sending its internal IPs instead of user IPs and presumably Nginx’ flood protection was kicking in. Updating Nginx configs solved the issue.

Browser cookie corruption(?) after site migration on Azure

Product Support

Falco (Falco) February 14, 2020, 5:56am 2

That is a well know Azure bug with some workarounds described here

Topic		Replies	Views
Invalid input for update_ip_address Self-hosting	17	2404	December 20, 2019
Issue after adding application gateway Product Support	0	448	February 14, 2019
Discourse installation on Azure not reachable Self-hosting	10	4672	August 17, 2021
Issues with an Azure install (need to configure inbound ports) Product Support	16	2773	February 22, 2017
Getting a 500 response when accessing Categories Index route Product Support	3	476	September 25, 2019

Browser cookie corruption(?) after site migration on Azure

Related topics