# 升级页面出现内部服务器错误
**URL:** https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331
**Category:** Support
**Created:** [2023 年8 月 8 日 11:14 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331 "2023-08-08T11:14:28Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@Campano](https://meta.discourse.org/u/Campano)
#### Post date: [2023 年8 月 8 日 11:14 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/1 "2023-08-08T11:14:29Z")
您好，
我在升级页面上遇到了一个错误，是否有记录在案的方法可以调试/报告这些情况？
感谢您的帮助！
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [2023 年8 月 8 日 13:13 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/2 "2023-08-08T13:13:16Z")
您应该能在 `/logs` 页面找到更多关于此错误的详细信息。如果您能在此分享您找到的信息，将有助于我们弄清楚问题所在。👍
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [2023 年8 月 8 日 15:10 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/3 "2023-08-08T15:10:04Z")
最近修复了一个与新版本编号系统相关的大问题。我找不到它，但通过命令行升级应该可以解决它。
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [2023 年8 月 8 日 15:15 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/4 "2023-08-08T15:15:41Z")
这个吗？
> [@Version Check job is raising an exception on latest tests-passed](https://meta.discourse.org/t/version-check-job-is-raising-an-exception-on-latest-tests-passed/274215/3):
>
> Thanks @merefield - the version check server needed some tweaks to understand the new -dev suffix on tests-passed version numbers. Should be working now: [7] pry(main)\> Discourse::VERSION::STRING =\> "3.2.0.beta1-dev" [8] pry(main)\> DiscourseHub.discourse\_version\_check =\> {"success"=\>"OK", "latestVersion"=\>"3.1.0.beta7", "criticalUpdates"=\>false, "missingVersionsCount"=\>0}
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [2023 年8 月 8 日 15:18 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/5 "2023-08-08T15:18:17Z")
那一个需要修复我们的中央版本检查服务器，所以现在应该到处都修复了。重新构建不会有任何改变。另外，我不认为那一个会影响 `/admin/upgrade` 路径 🤔
---
### Author:  [@Campano](https://meta.discourse.org/u/Campano)
#### Post date: [2023 年8 月 8 日 15:45 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/6 "2023-08-08T15:45:33Z")
日志显示触发错误时的情况如下：
> **屏幕截图**
>
> 
```plaintext
Message (7 copies reported)
ArgumentError (Malformed version number string < 3.1.0.beta6)
lib/version.rb:44:in `block in find_compatible_resource'
lib/version.rb:44:in `each'
lib/version.rb:44:in `sort_by'
lib/version.rb:44:in `find_compatible_resource'
lib/version.rb:79:in `find_compatible_git_resource'
app/controllers/application_controller.rb:420:in `block in with_resolved_locale'
app/controllers/application_controller.rb:420:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:74:in `call'
lib/middleware/content_security_policy.rb:12:in `call'
lib/middleware/anonymous_cache.rb:369:in `call'
config/initializers/100-quiet_logger.rb:20:in `call'
config/initializers/100-silence_logger.rb:29:in `call'
lib/middleware/enforce_hostname.rb:24:in `call'
lib/middleware/request_tracker.rb:228:in `call'
Backtrace
/usr/local/lib/ruby/site_ruby/3.2.0/rubygems/version.rb:223:in `initialize'
/usr/local/lib/ruby/site_ruby/3.2.0/rubygems/version.rb:206:in `new'
/usr/local/lib/ruby/site_ruby/3.2.0/rubygems/version.rb:206:in `new'
lib/version.rb:44:in `block in find_compatible_resource'
lib/version.rb:44:in `each'
lib/version.rb:44:in `sort_by'
lib/version.rb:44:in `find_compatible_resource'
lib/version.rb:79:in `find_compatible_git_resource'
plugins/docker_manager/lib/docker_manager/git_repo.rb:153:in `tracking_branch'
plugins/docker_manager/lib/docker_manager/git_repo.rb:100:in `tracking_ref'
```
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [2023 年8 月 8 日 15:53 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/7 "2023-08-08T15:53:30Z")
感谢 @Campano。我们曾希望这个问题能通过 [此提交](https://github.com/discourse/docker_manager/commit/4a493543deaefdc09b9b5649caaa6469c636403b) 来解决 docker\_manager 问题，但看起来我们还有更多工作要做。
在此期间，我建议遵循 @pfaffman 的建议，通过命令行重建（`./launcher rebuild app`）——这应该能使一切保持最新并正常工作。
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [2023 年8 月 8 日 21:04 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/8 "2023-08-08T21:04:34Z")
我已发布此主题，其中描述了错误以及如何恢复：
> [@Visiting /admin/upgrade may lead to a server error](https://meta.discourse.org/t/visiting-admin-upgrade-may-lead-to-a-server-error/274411):
>
> If you’re currently running a standard installation of Discourse earlier than v3.1.0.beta7 (or stable earlier than v3.0.6), there is a chance you will be met with this error when attempting to upgrade via the admin UI: Server Error while trying to load /admin/docker/repos Error code: 500 error To resolve the issue, you will need to run a [command-line rebuild](https://meta.discourse.org/t/how-do-i-update-my-docker-image-to-latest/23325): cd /var/discourse ./launcher rebuild app Once you’ve run a CLI upgrade, future upgrades…
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [2023 年8 月 10 日 16:22 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/9 "2023-08-10T16:22:02Z")
3 篇帖子已拆分为新主题：[访问 `/admin/upgrade` 时未定义的方法 `sub!`](https://meta.discourse.org/t/undefined-method-sub-when-visiting-admin-upgrade/274682)
---
### Author:  [@Campano](https://meta.discourse.org/u/Campano)
#### Post date: [2023 年8 月 10 日 17:30 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/10 "2023-08-10T17:30:58Z")
非常感谢您，@david，这对我来说很有效。
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [2023 年9 月 9 日 17:31 UTC](https://meta.discourse.org/t/internal-server-error-on-upgrade-page/274331/11 "2023-09-09T17:31:08Z")
此主题在上次回复后 30 天自动关闭。不再允许回复。