@mattab opened this Issue on December 17th 2016 Member

Report from email:

Update notification uses IP address instead of the (first) valid hostname from the config.


Er is een nieuwe versie van Piwik beschikbaar als update

U kunt automatisch updaten naar versie 3.0.0-rc2 of het pakket downloaden en handmatig installeren.

Voel je vrij om je idee├źn en suggesties te delen met het Piwik team:
  • should be instead "analytics.example.com" from the trusted_hosts array in the config.ini.php
@mattab commented on February 20th 2017 Member

This may be the same issue as: https://github.com/piwik/piwik/issues/6644

@pestevao commented on December 12th 2017

I think that they are differente issues.
It only happens to us this in email reports and always resolve to which is not used to configure any trusted_hosts entries.

@GavL89 commented on May 6th 2019

@tsteur - in relation to the closed issue #14413, no, none of the trusted hostnames are IP addresses. This is what the general section of our config.ini.pho file looks like

salt = "xxxxxxxxxx"
trusted_hosts[] = "analytics.ap-southeast-2.domain.com"
proxy_client_headers[] = "HTTP_X_FORWARDED_FOR"
proxy_host_headers[] = "HTTP_X_FORWARDED_HOST"
cors_domains[] = "*"
session_save_handler = dbtable
noreply_email_address = "noreply@domain.com"

@tsteur commented on May 6th 2019 Member

Was also reported here: https://github.com/matomo-org/matomo/issues/14413

I wonder: Maybe SettingsPiwik::getPiwikUrl should only store a url/hostname that is configured in the trusted hostnames once Matomo is installed and shouldn't overwrite a URL that isn't set as trusted url? Not sure if that would cause any issues but might be a good idea.

I've also tried updating the piwikUrl row in the database however it just gets updated by itself to the IP address of one of the servers.

@GavL89 it does look like the proxy header isn't actually forwarded cause the app should use it otherwise.

@tsteur commented on May 6th 2019 Member

@GavL89 I reckon we have kind of an idea where the problem is and will likely create a fix for this as part of 3.10 or 3.11

This Issue was closed on May 17th 2019
Powered by GitHub Issue Mirror