On the server side, this.connection.clientAddress occasionally returns 127.0.0.1 for some users at random, even though my server is not behind any proxy or load balancer. This behavior is inconsistent and I haven’t been able to identify the root cause or find any reliable solution to fix it yet. Any real solution ?
Do you have an small poc that reproduces it?
what is your host provider?
We don’t have clear reproduction steps, as the issue occurs very rarely. However, we update the IP address each time a user logs in using the following code. We use galaxy cloud for hosting.
Meteor.users.update(
{ _id: user._id, },
{
$set: {
ipAddress: this.connection.clientAddress,
},
}
);
I have given the piece of code. Please check and update for any solution
I will help you with this. I see you are very patient, so please give me till November.
2026.
@paulishca I’m hoping you mean November 2025, not 2026? We are not that patient that we can wait for more than a year. We use mostly default setup with Galaxy Cloud, standard functions and no proxy and we do pay for your services, so we expect that this is looked into on short term.
@Jacqueline
Nice to know you are using Galaxy, do you mind to create an simple application that uses a similar setup(meteor version, network settings, pkg.json config)? I can deploy this test-app into galaxy and create an script to try to catch that bug.
Since you use galaxy on it, you can open a ticket so everything wll be under NDA and prioritized.
Possibly your Meteor settings.json baseUrl getting overwritten or incorrectly set?
another thing, are you setting ROOT_URL?