I was trying to upgrade discourse from the admin control panel to the latest tests passed version from 3.3.0 and it gave the following errors ******************************************************** *** Please be patient, next steps might take a while *** *******************************************…

The solution appears to be to manually rebuild the image from the cli via ./launcher rebuild app. [이미지] Upgrade / Rebuilds Fail due to MaxMind DB EOL Self-hosting We now support the officially supported way of obtaining databases per: https://github.com/disco…

Also maxmind is requiring a user id number, so now would be a good time to add that Configure MAXMIND for reverse IP lookups .

Just a note from manually debugging this on our site, checking /logs showed us that our plugin causing this fatal error was Gamification, if you run your forum in safe mode with no plugins (?safe_mode=no_plugins) you should be able to temporarily switch off any offending plugins until you can get a …

관리자 패널을 통해 Discourse 3.3.0 beta1에서 beta2로 업그레이드 실패

지원 자체 호스팅

pfaffman (Jay Pfaffman) 5월 15, 2024, 7:01오전 3

또한 MaxMind는 사용자 ID를 요구하므로, 지금이 역방향 IP 조회를 위한 MAXMIND 구성을 추가하기에 좋은 시점입니다.

Setting DISCOURSE_MAXMIND_LICENSE_KEY breaks docker image/container build

글		댓글	조회수
Update from 3.0.0.beta16 to 3.1.0.beta2 Self-hosting	22	1523	4월 30, 2023
Failed to open TCP connection to geolite.maxmind.com:443 Self-hosting	3	1728	3월 31, 2020
Setting DISCOURSE_MAXMIND_LICENSE_KEY breaks docker image/container build Self-hosting maxmind	22	1706	5월 16, 2024
Upgrade failure mmdb_download (getaddrinfo: Name or service not known) Support	5	1686	2월 18, 2020
Upgrade Error from 2.4.0.beta8 to 2.4.0.beta9 Support	1	482	1월 15, 2020

관리자 패널을 통해 Discourse 3.3.0 beta1에서 beta2로 업그레이드 실패

Related topics