【问题标题】:Server denies request due to wrong Domain coming from Fritzbox由于来自 Fritzbox 的错误域,服务器拒绝请求
【发布时间】:2020-02-16 17:07:53
【问题描述】:

我正在尝试通过 IPv6 访问我的本地服务器,但由于证书问题而失败。

例如nextcloud 客户端出现以下错误:

$nextcloudcmd --trust --logdebug Nextcloud https://nextcloud.domain.de

10-20 12:47:43:798 [ info nextcloud.sync.accessmanager ]:   2 "" "https://nextcloud.domain.de/ocs/v1.php/cloud/capabilities?format=json" has X-Request-ID "19a2a694-1912-4813-b3f5-2d4d5720fa80"

10-20 12:47:43:799 [ info nextcloud.sync.networkjob ]:  OCC::JsonApiJob created for "https://nextcloud.domain.de" + "ocs/v1.php/cloud/capabilities" ""

10-20 12:47:43:955 [ info nextcloud.sync.account ]: "SSL-Errors happened for url  \"https://nextcloud.domain.de/ocs/v1.php/cloud/capabilities?format=json\" \tError in  QSslCertificate(\"3\", \"f9:8e:0f:4f:bd:4b:a3:5f\", \"hkXxG7tBu+SGaRSBZ9gRyw==\", \"<hostname>.domain.de\", \"<hostname>.domain.de\", QMap((1, \"www.fritz.nas\")(1, \"fritz.nas\")(1, \"<WiFi-Name>\")(1, \"www.myfritz.box\")(1, \"myfritz.box\")(1, \"www.fritz.box\")(1, \"fritz.box\")(1, \"<hostname>.domain.de\")), QDateTime(2019-10-19 12:32:25.000 UTC Qt::UTC), QDateTime(2038-01-15 12:32:25.000 UTC Qt::UTC)) : \"The host name did not match any of the valid hosts for this certificate\" ( \"The host name did not match any of the valid hosts for this certificate\" ) \n \tError in  QSslCertificate(\"3\", \"f9:8e:0f:4f:bd:4b:a3:5f\", \"hkXxG7tBu+SGaRSBZ9gRyw==\", \"<hostname>.domain.de\", \"<hostname>.domain.de\", QMap((1, \"www.fritz.nas\")(1, \"fritz.nas\")(1, \"<WiFi-Name>\")(1, \"www.myfritz.box\")(1, \"myfritz.box\")(1, \"www.fritz.box\")(1, \"fritz.box\")(1, \"<hostname>.domain.de\")), QDateTime(2019-10-19 12:32:25.000 UTC Qt::UTC), QDateTime(2038-01-15 
12:32:25.000 UTC Qt::UTC)) : \"The certificate is self-signed, and untrusted\" ( \"The certificate is self-signed, and untrusted\" ) \n " Certs are known and trusted! This is not an actual error.

10-20 12:47:43:964 [ warning nextcloud.sync.networkjob ]:   QNetworkReply::ProtocolInvalidOperationError "Server replied \"400 Bad Request\" to \"GET https://nextcloud.domain.de/ocs/v1.php/cloud/capabilities?format=json\"" QVariant(int, 400)

10-20 12:47:43:964 [ info nextcloud.sync.networkjob.jsonapi ]:  JsonApiJob of QUrl("https://nextcloud.domain.de/ocs/v1.php/cloud/capabilities?format=json") FINISHED WITH STATUS "ProtocolInvalidOperationError Server replied \"400 Bad Request\" to \"GET https://nextcloud.domain.de/ocs/v1.php/cloud/capabilities?format=json\""

10-20 12:47:43:964 [ warning nextcloud.sync.networkjob.jsonapi ]:   Network error:  "ocs/v1.php/cloud/capabilities" "Server replied \"400 Bad Request\" to \"GET https://nextcloud.domain.de/ocs/v1.php/cloud/capabilities?format=json\"" QVariant(int, 400)

10-20 12:47:43:964 [ debug default ]    [ main(int, char**)::<lambda ]: Server capabilities QJsonObject()
Error connecting to server

我想知道为什么 Fritzbox 会尝试通过 .domain.de 而不是 nextcloud.domain.de 请求。

谁能指出我正确的方向?

【问题讨论】:

  • 我注意到,无论出于何种原因,我都会在 Firefox 中打开不同的服务。但是,如果我然后按 CTRL+Shift+R,我会收到此错误:SEC_ERROR_INADEQUATE_KEY_USAGE

标签: subdomain ipv6 lets-encrypt fritzbox


【解决方案1】:

好的,我从站点(德语:https://avm.de/service/fritzbox/fritzbox-7580/wissensdatenbank/publication/show/3525_Zugriff-auf-HTTPS-Server-im-Heimnetz-nicht-moglich#zd)获得了信息,这使我得出以下结论。

由于您没有针对 IPv6 地址的 NAT,而且 fritzbox 也不能这样做,因此 IPv6 必须来自服务器。因此,我找到的一种解决方案是 ddclient。通过将其安装在您的 GNU\Linux 服务器上,它将更新您的 DynDNS 提供商处的 IPv6 地址。 但有一件事仍然是开放的。我无法更新 IPv4 和 IPv6。

【讨论】:

    猜你喜欢
    • 2021-04-11
    • 2012-04-18
    • 1970-01-01
    • 2012-10-24
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2020-04-15
    • 2020-04-19
    相关资源
    最近更新 更多