can't use the standard ports 80 and 443 on my network #1267

xcstatus · 2023-10-30T07:11:41Z

hi all,

I can't use the standard ports 80 and 443 on my network. How do I change the configuration for deployment? Since standard ports are not available, the reverse proxy cannot be deployed either.

mlsmaycon · 2023-10-30T14:16:47Z

Hey @xcstatus are you able to deploy the reverse proxy without the public access in these two ports? If so, there is a way to deploy it, but you will need to manage the SSL certificates.

xcstatus · 2023-10-31T02:39:01Z

Thank you for your reply.
All but the standard ports on my network are accessible via the Internet. SSL certificates can also be obtained in other ways.
Please tell me how I should operate.

MrChenhtlss · 2023-11-11T11:03:52Z

Thank you for your reply. All but the standard ports on my network are accessible via the Internet. SSL certificates can also be obtained in other ways. Please tell me how I should operate.

I have the same problem. Did you solve it? If so, can you help me?

xcstatus · 2023-11-13T05:00:05Z

Not solved yet, no way to deal with this problem, can only wait for the solution given by the @mlsmaycon

MrChenhtlss · 2023-11-13T06:51:13Z

xcstatus ***@***.***>于2023年11月13日周一13:00写道：

Not solved yet, no way to deal with this problem, can only wait for the solution given by the @mlsmaycon <https://github.com/mlsmaycon> — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SEJROTICPNK7WHDOCDYEGSOBAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGQ4DANBQG4> . You are receiving this because you commented.Message ID: ***@***.***>

If you have a solution please let me know thank you very much

mlsmaycon · 2023-11-14T08:34:03Z

Hello folks, we have a guide for running NetBird that you can use to configure NetBird to run behind a reverse-proxy like Nginx, Traefik or Caddyserver. See this link for more details. It covers the advanced guide setup, then you need to configure your reverse proxy.

For traefik and nginx you have some example templates:
Nginx.conf
docker-compose.yml.tmpl.traefik

For Caddyserver you can use the following example:

{
  debug
	servers :80,:443 {
    protocols h1 h2c
  }
}

:80,mydomain.example.com:443 {
    import security_headers
    # Signal
    reverse_proxy /signalexchange.SignalExchange/* h2c://signal:10000
    # Management
    reverse_proxy /api/* management:80
    reverse_proxy /management.ManagementService/* h2c://management:80
    # Dashboard
    reverse_proxy /* dashboard:80
}

You need to replace the references to the internal services according to your local environment. e.g., if your management is running on IP 192.168.0.100, replace h2c://management:80 with h2c://192.168.0.100:80

MrChenhtlss · 2023-11-14T08:38:11Z

Besides the docker-compose file, what else do I need to modify? Maycon Santos ***@***.***>于2023年11月14日周二16:34写道：

…

Hello folks, we have a guide for running NetBird that you can use to configure NetBird to run behind a reverse-proxy like Nginx, Traefik or Caddyserver. See this link <https://docs.netbird.io/selfhosted/selfhosted-guide#advanced-running-net-bird-behind-an-existing-reverse-proxy> for more details. It covers the advanced guide setup, then you need to configure your reverse proxy. For traefik and nginx you have some example templates: Nginx.conf <https://github.com/netbirdio/netbird/blob/d1d01a0611771b5604bf5806f385ebb9d70c58df/infrastructure_files/nginx.tmpl.conf> docker-compose.yml.tmpl.traefik <https://github.com/netbirdio/netbird/blob/d1d01a0611771b5604bf5806f385ebb9d70c58df/infrastructure_files/docker-compose.yml.tmpl.traefik> For Caddyserver you can use the following example: { debug servers :80,:443 { protocols h1 h2c } } :80,mydomain.example.com:443 { import security_headers # Signal reverse_proxy /signalexchange.SignalExchange/* h2c://signal:10000 # Management reverse_proxy /api/* management:80 reverse_proxy /management.ManagementService/* h2c://management:80 # Dashboard reverse_proxy /* dashboard:80 } You need to replace the references to the internal services according to your local environment. e.g., if your management is running on IP 192.168.0.100, replace h2c://management:80 with h2c://192.168.0.100:80 — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SBWGHSG2RDRD22YYG3YEMUINAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZG42DSOJXHE> . You are receiving this because you commented.Message ID: ***@***.***>

mlsmaycon · 2023-11-14T08:43:40Z

It depends on the scenario you are building. Can you share more about it @MrChenhtlss?

MrChenhtlss · 2023-11-14T08:49:38Z

Sorry I'm not a professional IT worker Maycon Santos ***@***.***>于2023年11月14日周二16:43写道：

…

It depends on the scenario you are building. Can you share more about it @MrChenhtlss <https://github.com/MrChenhtlss>? — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SAQT7QLQIPIIUQVAQLYEMVMPAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZG43DGMJYGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

MrChenhtlss · 2023-11-14T08:53:38Z

Or I would just use express install. Doc provides an advanced installation method, but I can't understand it. T oy ***@***.***>于2023年11月14日周二16:49写道：

…

Sorry I'm not a professional IT worker Maycon Santos ***@***.***>于2023年11月14日周二16:43写道： > It depends on the scenario you are building. Can you share more about it > @MrChenhtlss <https://github.com/MrChenhtlss>? > > — > Reply to this email directly, view it on GitHub > <#1267 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BC6T5SAQT7QLQIPIIUQVAQLYEMVMPAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZG43DGMJYGE> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

mlsmaycon · 2023-11-14T08:58:10Z

@MrChenhtlss Maybe you can share more about your current server setup, like what is running on ports 80 and 443, do you have a proxy like nginx or others?

MrChenhtlss · 2023-11-14T08:59:47Z

80,443 running nginx Maycon Santos ***@***.***>于2023年11月14日周二16:58写道：

…

@MrChenhtlss <https://github.com/MrChenhtlss> Maybe you can share more about your current server setup, like what is running on ports 80 and 443, do you have a proxy like nginx or others? — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SH3YIWLPXNGOUOP2L3YEMXC3AVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZG44DQMZXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

MrChenhtlss · 2023-11-14T09:17:51Z

I have another server but my service provider disabled my ports 80 and 443 other ports are accessible from the internet T oy ***@***.***>于2023年11月14日周二16:59写道：

…

80,443 running nginx Maycon Santos ***@***.***>于2023年11月14日周二16:58写道： > @MrChenhtlss <https://github.com/MrChenhtlss> Maybe you can share more > about your current server setup, like what is running on ports 80 and 443, > do you have a proxy like nginx or others? > > — > Reply to this email directly, view it on GitHub > <#1267 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BC6T5SH3YIWLPXNGOUOP2L3YEMXC3AVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZG44DQMZXGI> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

xcstatus · 2023-11-20T01:54:48Z

Any progress so far?

xcstatus · 2023-12-18T06:45:15Z

@MrChenhtlss

The deployment script was modified and the deployment was successful over a non-standard port. But you will need to get your own domain certificate.
Change the port number in the script.
Add the domain certificate configuration to the caddy configuration file.
3. Change the redirect Settings in zitdel.
4. Modify the address of the HttpConfig node in the renderManagementJson method, and add the port.

修改了部署脚本，通过非标准端口部署成功了。但是需要自己申请域名证书。

修改脚本中的端口号。
在caddy配置文件中增加域名证书配置。
修改zitdel中的重定向设置。
修改renderManagementJson方法中HttpConfig节点下地址，需要增加端口。

MrChenhtlss · 2023-12-18T06:47:50Z

非常感谢，方便给我更详细的操作方法么 xcstatus ***@***.***>于2023年12月18日周一14:45写道：

…

image.png (view on web) <https://github.com/netbirdio/netbird/assets/40375067/0391245a-a212-4a40-9d59-8721b77c4071> @MrChenhtlss <https://github.com/MrChenhtlss> The deployment script was modified and the deployment was successful over a non-standard port. But you will need to get your own domain certificate. Change the port number in the script. Add the domain certificate configuration to the caddy configuration file. 3. Change the redirect Settings in zitdel. 4. Modify the address of the HttpConfig node in the renderManagementJson method, and add the port. 修改了部署脚本，通过非标准端口部署成功了。但是需要自己申请域名证书。 1. 修改脚本中的端口号。 2. 在caddy配置文件中增加域名证书配置。 3. 修改zitdel中的重定向设置。 4. 修改renderManagementJson方法中HttpConfig节点下地址，需要增加端口。 — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SGW23IFWUIDM72P7WDYJ7RALAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGY2DKNZZGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

xcstatus · 2023-12-18T07:34:25Z

晚点我整理下，现在发现了一个问题通过pre-shard key 无法在客户端登录

MrChenhtlss · 2023-12-18T14:55:45Z

好的，非常感谢，但是官方似乎有通过nginx的部署方法，但是由于能力有限，无法完全理解官方doc的内容 status ***@***.***>于2023年12月18日周一15:34写道：

…

晚点我整理下，现在发现了一个问题通过pre-shard key 无法在客户端登录 — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SFJJZ7LL2J43KD4ZWDYJ7WYZAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGY4TINZTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

xcstatus · 2023-12-18T15:30:33Z

Netbird安装.md
getting-started-with-zitadel-xc.zip
@MrChenhtlss 这是我修改后的脚本和修改、安装说明。
@mlsmaycon Problem solved. I closed the problem. Thank you very much

MrChenhtlss · 2023-12-18T15:31:30Z

OK,这真的太棒了 xcstatus ***@***.***>于2023年12月18日周一23:30写道：

…

Netbird安装.md <https://github.com/netbirdio/netbird/files/13705518/Netbird.md> getting-started-with-zitadel-xc.zip <https://github.com/netbirdio/netbird/files/13705521/getting-started-with-zitadel-xc.zip> @MrChenhtlss <https://github.com/MrChenhtlss> 这是我修改后的脚本和修改、安装说明。 @mlsmaycon <https://github.com/mlsmaycon> Problem solved. I closed the problem. Thank you very much — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SHRY6PUDQQQAMXG44TYKBOSHAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRQHAZDAMZTGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

jiangslee · 2023-12-19T03:17:35Z

Netbird安装.md getting-started-with-zitadel-xc.zip @MrChenhtlss 这是我修改后的脚本和修改、安装说明。 @mlsmaycon Problem solved. I closed the problem. Thank you very much

真香！

我迭代下，端口号改成交互输入，域名证书改成自动匹配。

操作步骤：

mkdir certs
在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key

~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem

export NETBIRD_DOMAIN=netbird.my-domain.com
bash getting-started-with-zitadel-xc.sh
按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号，比如我上图的TCP：8088,8443; UDP ports: 3478, 49152-65535）

getting-started-with-zitadel-xc-prompt.sh.zip

目前证书需要手动维护，要是有大佬能改成自动获取及更新证书就更好了。

xcstatus · 2023-12-19T05:15:23Z

👍。我一直想要这样做，但是我不太懂shell语法，所以不敢对脚本做太大的修改。这个对脚本的修改是否有必要提个pr给官方？但是需要兼容下不需要修改端口号的情况。

MrChenhtlss · 2023-12-19T05:17:55Z

Netbird安装.md getting-started-with-zitadel-xc.zip @MrChenhtlss 这是我修改后的脚本和修改、安装说明。 @mlsmaycon Problem solved. I closed the problem. Thank you very much

真香！

我迭代下，端口号改成交互输入，域名证书改成自动匹配。

操作步骤：

mkdir certs

在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key
~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem
export NETBIRD_DOMAIN=netbird.my-domain.com

bash getting-started-with-zitadel-xc.sh

按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号，比如我上图的TCP：8088,8443; UDP ports: 3478, 49152-65535）

getting-started-with-zitadel-xc-prompt.sh.zip

目前证书需要手动维护，要是有大佬能改成自动获取及更新证书就更好了。

这个真的非常棒，ssl可以申请腾讯云各大云厂商为期一年的free证书

xcstatus · 2023-12-21T02:03:44Z

证书自动维护可以考虑下caddy的dns质询组件。https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148

jiangslee · 2023-12-21T03:32:24Z

官方的脚本默认就是caddy自动获取证书的，不过你改的手动证书方案更适合我 😋

MrChenhtlss · 2023-12-21T07:01:44Z

Netbird安装.md getting-started-with-zitadel-xc.zip @MrChenhtlss 这是我修改后的脚本和修改、安装说明。 @mlsmaycon Problem solved. I closed the problem. Thank you very much

真香！

我迭代下，端口号改成交互输入，域名证书改成自动匹配。

操作步骤：

mkdir certs

在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key
~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem
export NETBIRD_DOMAIN=netbird.my-domain.com

bash getting-started-with-zitadel-xc.sh

按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号，比如我上图的TCP：8088,8443; UDP ports: 3478, 49152-65535）

getting-started-with-zitadel-xc-prompt.sh.zip

目前证书需要手动维护，要是有大佬能改成自动获取及更新证书就更好了。

据说“acme.sh” 基于acme可以自动续签SSL证书，但是由于我不是从事IT运维的能提供的参考非常有限，希望您可以参考下是否可行
It is said that "acme.sh" can automatically update acme-based SSL certificates. Since I have no ability to engage in IT operation and maintenance, the reference provided is very limited. I hope everyone can refer to it to see if it is feasible.

MrChenhtlss · 2023-12-21T07:32:01Z

Netbird安装.md getting-started-with-zitadel-xc.zip @MrChenhtlss 这是我修改后的脚本和修改、安装说明。 @mlsmaycon Problem solved. I closed the problem. Thank you very much

真香！

我迭代下，端口号改成交互输入，域名证书改成自动匹配。

操作步骤：

mkdir certs

在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key
~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem
export NETBIRD_DOMAIN=netbird.my-domain.com

bash getting-started-with-zitadel-xc.sh

按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号，比如我上图的TCP：8088,8443; UDP ports: 3478, 49152-65535）

getting-started-with-zitadel-xc-prompt.sh.zip

目前证书需要手动维护，要是有大佬能改成自动获取及更新证书就更好了。

请问是否将8080端口写入到脚本可以支持交互式输入，因为我的8080端口已经被其他进程占用，可以的话那就太棒了！！！！

jiangslee · 2023-12-21T09:17:54Z

Netbird安装.md getting-started-with-zitadel-xc.zip @MrChenhtlss 这是我修改后的脚本和修改、安装说明。 @mlsmaycon Problem solved. I closed the problem. Thank you very much

真香！
我迭代下，端口号改成交互输入，域名证书改成自动匹配。
操作步骤：

mkdir certs

在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key
~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem
export NETBIRD_DOMAIN=netbird.my-domain.com

bash getting-started-with-zitadel-xc.sh

按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号，比如我上图的TCP：8088,8443; UDP ports: 3478, 49152-65535）

getting-started-with-zitadel-xc-prompt.sh.zip
目前证书需要手动维护，要是有大佬能改成自动获取及更新证书就更好了。
请问是否将8080端口写入到脚本可以支持交互式输入，因为我的8080端口已经被其他进程占用，可以的话那就太棒了！！！！

好像那个8080没有实际用途，等会给你改一个交互输入修改8080的脚本

jiangslee · 2023-12-21T09:33:02Z

Netbird安装.md getting-started-with-zitadel-xc.zip @MrChenhtlss 这是我修改后的脚本和修改、安装说明。 @mlsmaycon Problem solved. I closed the problem. Thank you very much

真香！
我迭代下，端口号改成交互输入，域名证书改成自动匹配。
操作步骤：

mkdir certs

在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key
~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem
export NETBIRD_DOMAIN=netbird.my-domain.com

bash getting-started-with-zitadel-xc.sh

按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号，比如我上图的TCP：8088,8443; UDP ports: 3478, 49152-65535）

getting-started-with-zitadel-xc-prompt.sh.zip
目前证书需要手动维护，要是有大佬能改成自动获取及更新证书就更好了。
请问是否将8080端口写入到脚本可以支持交互式输入，因为我的8080端口已经被其他进程占用，可以的话那就太棒了！！！！

getting-started-with-zitadel-xc.sh.zip

@MrChenhtlss 你试试看。

Beatirce · 2023-12-25T07:24:41Z

改回来了，然后我按照md文件中说明修改后执行时提示的错误，麻烦帮忙看看是哪里的问题…

如果没有必要，不需要修改$NETBIRD_DOMAIN节点下的配置，修改配置的前提是你知道自己在做什么。

certs文件夹是需要在脚本执行的目录中创建的。

xcstatus · 2023-12-25T07:55:27Z

看不出来有什么问题，怀疑是 crdb这个服务没有启动起来。

Beatirce · 2023-12-25T08:17:05Z

看不出来有什么问题，怀疑是 crdb这个服务没有启动起来。

感谢，我看看这个服务。

jiangslee · 2023-12-25T09:54:19Z

看不出来有什么问题，怀疑是 crdb这个服务没有启动起来。

感谢，我看看这个服务。

操作步骤：

mkdir certs
在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key

~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem

export NETBIRD_DOMAIN=netbird.my-domain.com
bash getting-started-with-zitadel-xc.sh

按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号; UDP ports: 3478, 49152-65535）

MrChenhtlss · 2023-12-25T09:56:05Z

如果在国内服务器上部署的话需要注释掉脚本中的 h1 h2，另外再把所需的docker镜像手动pull一下 jiangslee ***@***.***>于2023年12月25日周一17:54写道：

…

看不出来有什么问题，怀疑是 crdb这个服务没有启动起来。感谢，我看看这个服务。操作步骤： 1. mkdir certs 2. 在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key ~/docker-netbird# tree certs certs ├── netbird.my-domain.com.key └── netbird.my-domain.com.pem 1. export NETBIRD_DOMAIN=netbird.my-domain.com 2. bash getting-started-with-zitadel-xc.sh 按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号; UDP ports: 3478, 49152-65535） — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SDZSR4OK4Z2QFPE3R3YLFENNAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYHA4TQMBSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

jiangslee · 2023-12-25T09:57:50Z

@MrChenhtlss 我也是国内服务器部署，没有注释h1 h2也能跑，关键是需要提前解释好域名、提前放行端口。

MrChenhtlss · 2023-12-25T10:01:47Z

前两天部署的时候如果不注视掉 h1 h2 会卡在zitadel 无法进行下一步 jiangslee ***@***.***>于2023年12月25日周一17:58写道：

…

@MrChenhtlss <https://github.com/MrChenhtlss> 我也是国内服务器部署，没有注释h1 h2也能跑，关键是需要*提前解释好域名*、*提前放行端口*。 — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SGTVQ5CQ6KRGYREQW3YLFE2TAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYHA4TSNZUGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

xcstatus · 2023-12-25T15:31:35Z

caddy.zip
可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。
其余云服务上可以在Dockerfile中替换对应的插件就行

jiangslee · 2023-12-26T09:03:16Z

caddy.zip 可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。其余云服务上可以在Dockerfile中替换对应的插件就行

这是要自己构建caddy的docker镜像吗？

xcstatus · 2023-12-26T09:54:16Z

是的发自我的 iPhone在 2023年12月26日，17:03，jiangslee ***@***.***> 写道： caddy.zip 可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。其余云服务上可以在Dockerfile中替换对应的插件就行这是要自己构建caddy的docker镜像吗？ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>

xcstatus · 2023-12-26T09:56:36Z

使用构建的caddy-dnspod镜像可以正常运行。证书也可以自动获取。但是我不太清楚怎么把构建过程编写成脚本，通过脚本指定caddy版本、dns质询插件发自我的 iPhone在 2023年12月26日，17:03，jiangslee ***@***.***> 写道： caddy.zip 可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。其余云服务上可以在Dockerfile中替换对应的插件就行这是要自己构建caddy的docker镜像吗？ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>

MrChenhtlss · 2023-12-27T11:16:49Z

不知道为什么我无法打开这个issues xcstatus ***@***.***>于2023年12月26日周二17:56写道：

…

使用构建的caddy-dnspod镜像可以正常运行。证书也可以自动获取。但是我不太清楚怎么把构建过程编写成脚本，通过脚本指定caddy版本、dns质询插件发自我的 iPhone在 2023年12月26日，17:03，jiangslee ***@***.***> 写道： caddy.zip 可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。其余云服务上可以在Dockerfile中替换对应的插件就行这是要自己构建caddy的docker镜像吗？ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SGXJ2ET3D27IZXPASDYLKNN7AVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGQZDCMZVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

xhwwstudio · 2024-01-14T14:55:26Z

看不出来有什么问题，怀疑是 crdb这个服务没有启动起来。

感谢，我看看这个服务。

操作步骤：
1. mkdir certs

2. 在certs目录放好与域名一致的证书文件，如netbird.my-domain.com.pem，netbird.my-domain.com.key
~/docker-netbird# tree certs
certs
├── netbird.my-domain.com.key
└── netbird.my-domain.com.pem
3. export NETBIRD_DOMAIN=netbird.my-domain.com

4. bash getting-started-with-zitadel-xc.sh
按提示输入好端口号（请提前进行域名解释和及安全组端口放行：你自定义的端口号; UDP ports: 3478, 49152-65535）

请问大佬，下载的这个文件和certs放在一个文件夹下边么？还是放里CERTS里边？

xcstatus · 2024-01-14T17:00:56Z

docker-netbird
├── certs
└── getting-started-with-zitadel-xc-prompt.sh
同一个文件夹下

liuyishengaaa · 2024-01-17T08:39:17Z

使用构建的caddy-dnspod镜像可以正常运行。证书也可以自动获取。但是我不太清楚怎么把构建过程编写成脚本，通过脚本指定caddy版本、dns质询插件发自我的 iPhone在 2023年12月26日，17：03，jiangslee @.> 写道： caddy.zip 可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。其余云服务上可以在Dockerfile中替换对应的插件就行这是要自己构建caddy的docker镜像吗？ - 直接回复此电子邮件，在 GitHub 上查看或取消订阅。您收到此消息是因为您修改了打开/关闭状态。邮件 ID：@.>

可以使用cloudflare申请的免费15年证书，上面您提到的自动续签能有个详细操作流程就完美了。

xcstatus · 2024-01-17T10:20:52Z

使用构建的caddy-dnspod镜像可以正常运行。证书也可以自动获取。但是我不太清楚怎么把构建过程编写成脚本，通过脚本指定caddy版本、dns质询插件发自我的 iPhone在 2023年12月26日，17：03，jiangslee @.> 写道： caddy.zip 可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。其余云服务上可以在Dockerfile中替换对应的插件就行这是要自己构建caddy的docker镜像吗？ - 直接回复此电子邮件，在 GitHub 上查看或取消订阅。您收到此消息是因为您修改了打开/关闭状态。邮件 ID：@.>

可以使用cloudflare申请的免费15年证书，上面您提到的自动续签能有个详细操作流程就完美了。

这里有配置的方法。
#1464
这是我使用的构建caddy-dnspod的脚本，但是我不知道如何改造成一个通用的脚本。
caddy-builder.tar.gz

shangkouyou · 2024-08-03T07:12:31Z

getting-started-with-zitadel-xc.sh.zip

可以跑了

这个好棒啊我也跑起来了很完美现在唯一不足的就是我想改这个默认的100.xx.xx.xx这个网段可以自定义吗大佬

shangkouyou · 2024-08-04T17:29:03Z

有办法修改默认的网段嘛 100.91.0.0/24.这个

使用构建的caddy-dnspod镜像可以正常运行。证书也可以自动获取。但是我不太清楚怎么把构建过程编写成脚本，通过脚本指定caddy版本、dns质询插件发自我的 iPhone在 2023年12月26日，17：03，jiangslee @.> 写道： caddy.zip 可以试试这个，构建caddy-dnspod，支持腾讯云dns质询。可以自动签名。其余云服务上可以在Dockerfile中替换对应的插件就行这是要自己构建caddy的docker镜像吗？ - 直接回复此电子邮件，在 GitHub 上查看或取消订阅。您收到此消息是因为您修改了打开/关闭状态。邮件 ID：@.>

可以使用cloudflare申请的免费15年证书，上面您提到的自动续签能有个详细操作流程就完美了。

这里有配置的方法。
#1464
这是我使用的构建caddy-dnspod的脚本，但是我不知道如何改造成一个通用的脚本。
caddy-builder.tar.gz

jiangslee · 2024-08-05T00:26:34Z

@shangkouyou 默认给的好像是100.x.x.x/16网段，一般不会冲突，为什么要改为/24？

shangkouyou · 2024-08-05T01:53:05Z

@shangkouyou* 默认给的好像是100.x.x.x/16网段，一般不会冲突，为什么要改为/24？

我主要是想改100.xxx.xxx.xxx 想改成自己喜欢的内网网段

jiangslee · 2024-08-05T02:35:54Z

@shangkouyou #1633

真不建议你改。

shangkouyou · 2024-08-05T02:58:12Z

@shangkouyou* #1633*

真不建议你改。

好的吧谢谢你

shangkouyou · 2024-08-09T03:37:21Z

@shangkouyou* #1633*

真不建议你改。

佬我还行问哦你上面的脚本执行后安装的是老的版本可以升级最新的吗

1350962574 · 2024-09-16T08:50:36Z

证书自动维护可以考虑下caddy的dns质询组件。https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148

@xcstatus @jiangslee
这是我认为最好的方式，以Cloudflare举例可以使用iarekylew00t/caddy-cloudflare:latest镜像通过 CF 的 API 自动签发并续期，当然网上也有构建好并支持 dnspod，aliyun的docker镜像，配合上方大佬改进的安装脚本实现非 80,443完美SSL。

liuyishengaaa · 2024-10-28T02:43:23Z

证书自动维护可以考虑下caddy的dns质询组件。https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148

@xcstatus @jiangslee 这是我认为最好的方式，以Cloudflare举例可以使用iarekylew00t/caddy-cloudflare:latest镜像通过 CF 的 API 自动签发并续期，当然网上也有构建好并支持 dnspod，aliyun的docker镜像，配合上方大佬改进的安装脚本实现非 80,443完美SSL。

你能提供详细的部署流程？

MrChenhtlss · 2024-10-28T02:46:05Z

按照上方大佬提供的脚本部署完成后修改compose与Caddyfile文件即可 liuyishengaaa ***@***.***>于2024年10月28日周一10:43写道：

…

证书自动维护可以考虑下caddy的dns质询组件。 https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148 @xcstatus <https://github.com/xcstatus> @jiangslee <https://github.com/jiangslee> 这是我认为最好的方式，以Cloudflare举例可以使用 iarekylew00t/caddy-cloudflare:latest镜像通过 CF 的 API 自动签发并续期，当然网上也有构建好并支持 dnspod，aliyun的docker镜像，配合上方大佬改进的安装脚本实现非 80,443完美SSL。 [image: image] <https://private-user-images.githubusercontent.com/48989077/367694561-72381bf6-319b-4d40-b765-dcbc19ab80cf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzAwODM1MTcsIm5iZiI6MTczMDA4MzIxNywicGF0aCI6Ii80ODk4OTA3Ny8zNjc2OTQ1NjEtNzIzODFiZjYtMzE5Yi00ZDQwLWI3NjUtZGNiYzE5YWI4MGNmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDI4VDAyNDAxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE1NzM4ZmE4MjFjZTM5OGZkOTljODZjYTBmMzYxODY2MTM2ODgwOTcwMjYzOTQ0MDJlNjdiZjY1NDZjNTc4NWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.FAyq9McJ6n8-5DmvDQ1V7eN3uzJrKQHcRozfzdh7Ipw> [image: image] <https://private-user-images.githubusercontent.com/48989077/367694610-0c758b1b-83f9-4e3b-9d6a-2c4cbd8fbfb6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzAwODM1MTcsIm5iZiI6MTczMDA4MzIxNywicGF0aCI6Ii80ODk4OTA3Ny8zNjc2OTQ2MTAtMGM3NThiMWItODNmOS00ZTNiLTlkNmEtMmM0Y2JkOGZiZmI2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDI4VDAyNDAxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTExZWZlNmNkZjMwNjUzYzk5ZDcyZTEzNzAzNzY1ZjZiOWFjNzNjNjg2ZDMyMmQwMzZjMzUwMDI5Y2JlMWMwZWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.CiqNR-mfWCRAFAFlA0uBvpflJu6uYuWIZfncZpM8yBA> [image: image] <https://private-user-images.githubusercontent.com/48989077/367700029-e3ae9016-48ce-478a-883d-ed212d68ff4d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzAwODM1MTcsIm5iZiI6MTczMDA4MzIxNywicGF0aCI6Ii80ODk4OTA3Ny8zNjc3MDAwMjktZTNhZTkwMTYtNDhjZS00NzhhLTg4M2QtZWQyMTJkNjhmZjRkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDI4VDAyNDAxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA4YzI2YmRmMzc4ZGFmNDQwZDdjMWVkNjJlNmVmMDcxNTYwZmEyMmY2MDA4ZTI3NzQ1Y2IwOGI1Y2Y5MmI2MmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0._qauzexEMjtZG7060e6_-_YqPPsHLPsAKNaMpkIpRr8> 你能提供详细的部署流程？ — Reply to this email directly, view it on GitHub <#1267 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC6T5SCC2JAQ2PF6N374TB3Z5WQGFAVCNFSM6AAAAAA6VQ3QOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQGQZDGNBZGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

xcstatus closed this as completed Dec 18, 2023

jiangslee mentioned this issue Dec 26, 2023

getting-started-with-zitadel.sh #1408

Open

jiangslee mentioned this issue Dec 26, 2023

quickstart script support custom ports and ssl certificates #1410

Closed

6 tasks

xcstatus mentioned this issue Jan 13, 2024

feat(Self-hosting NetBird script):support custom service port and DNS… #1464

Closed

6 tasks

jiangslee mentioned this issue Mar 16, 2024

Run netbird locally #1716

Open

can't use the standard ports 80 and 443 on my network #1267

can't use the standard ports 80 and 443 on my network #1267

Comments

xcstatus commented Oct 30, 2023

mlsmaycon commented Oct 30, 2023

xcstatus commented Oct 31, 2023

MrChenhtlss commented Nov 11, 2023

xcstatus commented Nov 13, 2023

MrChenhtlss commented Nov 13, 2023 via email

mlsmaycon commented Nov 14, 2023

MrChenhtlss commented Nov 14, 2023 via email

mlsmaycon commented Nov 14, 2023

MrChenhtlss commented Nov 14, 2023 via email

MrChenhtlss commented Nov 14, 2023 via email

mlsmaycon commented Nov 14, 2023

MrChenhtlss commented Nov 14, 2023 via email

MrChenhtlss commented Nov 14, 2023 via email

xcstatus commented Nov 20, 2023

xcstatus commented Dec 18, 2023

MrChenhtlss commented Dec 18, 2023 via email

xcstatus commented Dec 18, 2023

MrChenhtlss commented Dec 18, 2023 via email

xcstatus commented Dec 18, 2023

MrChenhtlss commented Dec 18, 2023 via email

jiangslee commented Dec 19, 2023 • edited Loading

xcstatus commented Dec 19, 2023

MrChenhtlss commented Dec 19, 2023

xcstatus commented Dec 21, 2023

jiangslee commented Dec 21, 2023

MrChenhtlss commented Dec 21, 2023

MrChenhtlss commented Dec 21, 2023

jiangslee commented Dec 21, 2023

jiangslee commented Dec 21, 2023 • edited Loading

Beatirce commented Dec 25, 2023

xcstatus commented Dec 25, 2023

Beatirce commented Dec 25, 2023

jiangslee commented Dec 25, 2023

MrChenhtlss commented Dec 25, 2023 via email

jiangslee commented Dec 25, 2023

MrChenhtlss commented Dec 25, 2023 via email

xcstatus commented Dec 25, 2023 • edited Loading

jiangslee commented Dec 26, 2023

xcstatus commented Dec 26, 2023 via email

xcstatus commented Dec 26, 2023 via email

MrChenhtlss commented Dec 27, 2023 via email

xhwwstudio commented Jan 14, 2024

xcstatus commented Jan 14, 2024

liuyishengaaa commented Jan 17, 2024

xcstatus commented Jan 17, 2024

shangkouyou commented Aug 3, 2024

shangkouyou commented Aug 4, 2024

jiangslee commented Aug 5, 2024

shangkouyou commented Aug 5, 2024

jiangslee commented Aug 5, 2024 • edited Loading

shangkouyou commented Aug 5, 2024

shangkouyou commented Aug 9, 2024

1350962574 commented Sep 16, 2024 • edited Loading

liuyishengaaa commented Oct 28, 2024

MrChenhtlss commented Oct 28, 2024 via email

jiangslee commented Dec 19, 2023 •

edited

Loading

jiangslee commented Dec 21, 2023 •

edited

Loading

xcstatus commented Dec 25, 2023 •

edited

Loading

jiangslee commented Aug 5, 2024 •

edited

Loading

1350962574 commented Sep 16, 2024 •

edited

Loading