Realm 对象服务器的 Https 代理不起作用

debugcn 发表于 Dev

王嘉尔

我似乎无法获得Realm Object Server运行的https代理。我遵循了文档中的每一步，其中包括编辑 configuration.yml 文件以进行更改：

proxy.https.enable: true  
proxy.https.listen_address: ::  
proxy.https.listen_port: 9443  
proxy.https.certificate_path: 'cert_path'
proxy.https.private_key_path: 'private_key_path'

当我访问http://example.com:9080时很好，但访问https://example.com:9443不起作用 - 我已经验证路径正确，并且证书/私钥组合有效。

任何配置此功能的帮助将不胜感激，因为我正在尝试使应用程序符合 Apple 的 ATS 要求！

拉杜·图图亚努

Realm Object Server 由“realm”用户启动，您应该检查该用户是否具有访问证书的权限。

这是使用letencrypt设置 https 的说明列表！在 Ubuntu 16.04 上，也许它有助于确定您的问题：

安装 ROS、letencrypt 并生成证书

curl -s https://packagecloud.io/install/repositories/realm/realm/script.deb.sh | sudo bash

apt-get install realm-object-server-developer
apt-get install letsencrypt

letsencrypt certonly --standalone -d ${mydomain.com}

# set up permissions for the realm user on /etc/letsencrypt.
sudo groupadd ssl
sudo usermod -a -G ssl realm
sudo chgrp -R ssl /etc/letsencrypt
sudo chmod -R g=rX /etc/letsencrypt

编辑配置以在“代理”部分启用 ssl

部分/etc/realm/configuration.yml：

  https:
    ## Whether or not to enable the HTTPS proxy module. It enables multiplexing requests
    ## by forwarding incoming requests on a single port to all services.
    ## Note that even if it enabled, the HTTPS proxy will only start if supplied
    ## with a valid pair of certificates through certificate_path and private_key_path below.
    enable: true

    ## The path to the certificate and private keys (in PEM format) that will be used
    ## to set up the HTTPS server accepting connections.
    ## These configuration options are MANDATORY to start the HTTPS proxy module.
    certificate_path: '/etc/letsencrypt/live/${mydomain.com}/cert.pem'
    private_key_path: '/etc/letsencrypt/live/${mydomain.com}/privkey.pem'

    ## The address/interface on which the HTTPS proxy module should listen. This defaults
    ## to 127.0.0.1. If you wish to listen on all available interfaces,
    ## uncomment the following line.
    listen_address: '::'

    ## The port that the HTTPS proxy module should bind to.
    # listen_port: 9443