Hey people, When running a docker based install, and setting DISCOURSE_MAXMIND_LICENSE_KEY the image creation process aborts with this error: /var/www/discourse/lib/discourse_ip_info.rb:48:in `mmdb_download': undefined method `path' for nil:NilClass (NoMethodError) filename = File.basename(gz…

You’re welcome. Just let me know if I shall try something or if you need additional info. :slightly_smiling_face:

The key id definitely valid. And it’s also entered correctly as the whole stuff is fully automated via Ansible. The same key works at other locations in the playbook like a charm (and there are also no rate-limiting issues). Feels like the URL is just not working.

Since I have been having the same problem and can confirm that when clearing out the license key, my rebuild problems magically goes away. I have even over a couple of days, tried my best to dig into the problem. I think I have it right, but I might aswell be wrong. During build, it seems like th…

Just to bump this is still an issue, just had the exact same when adding the key and uncommenting the setting in app.yml.

Got this notice when updating from main branch today: Downloading MaxMindDB... MaxMind IP database updates require a license Please set DISCOURSE_MAXMIND_LICENSE_KEY to one you generated at https://www.maxmind.com MaxMind IP database updates require a license Please set DISCOURSE_MAXMIND_LICENSE_K…

I think that’s expected without a maxmind key?

We run into the same issue. Adding DISCOURSE_MAXMIND_ACCOUNT_ID to the env fixed this for me. Strike that, I first assumed that the container build successfully, but that was not the case.

Happy cakeday! AFAIK, this issue has been fixed, (to cover bases) your key and account ID are correct, right?

Did you rebuld recently? What error do you have?

Yes, this was today. The error OP posted.

Das Setzen von DISCOURSE_MAXMIND_LICENSE_KEY bricht den Docker-Image-/Container-Build

Unterstützung Installation

Firepup650 (Firepup Sixfifty) 9. Mai 2024 um 13:01 12

Alles Gute zum Geburtstag!
Soweit ich weiß, wurde dieses Problem behoben. (Nur zur Sicherheit) Sind Ihr Schlüssel und Ihre Konto-ID korrekt?

Thema		Antworten	Aufrufe
Rebuilding always fails when the MAXMIND daily limit is exhausted Bug maxmind , dev-ops , fixed	63	1112	5. August 2024
Update from 3.0.0.beta16 to 3.1.0.beta2 Self-hosting	22	1353	30. April 2023
Upgrade / Rebuilds Fail due to MaxMind DB EOL Self-hosting maxmind	15	8626	6. März 2020
Upgrade discourse fails from 3.3.0 beta1 to beta2 via admin panel Self-hosting	4	444	14. Juni 2024
Discourse down after failed web update, rebuild & doctor not helping Self-hosting	8	671	16. April 2023

Das Setzen von DISCOURSE_MAXMIND_LICENSE_KEY bricht den Docker-Image-/Container-Build

Verwandte Themen