[GH-ISSUE #4781] Cannot connect to Raspberry Pi via Amazon Lightsail instance

gitea-mirror commented

2026-05-05 14:25:05 -06:00

Owner

Copy link

Originally created by @IanAber on GitHub (May 3, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4781

Bug Description

I am running the server on a Lightsail instance with Amazon Linux 2023 on AMD64 hardware with a client running the latest 64 bit Bookwork Linux on a Raspberry Pi. When trying to connect to the https WEB site in Chrome from a Mac I get...

ERR_SSL_UNRECOGNIZED_NAME_ALERT

If I use an AMD64 linux client everything works perfectly. It is just the ARM64 Raspberry Pi that returns this error.

I do not see anything in the logs at either end, client or server.

What should I look for to troubleshoot this?

frpc Version

0.62.1

frps Version

0.62.1

System Architecture

linux/amd64 server ; linux/ARM64 client

Configurations

Client config =

`
serverAddr = "cloud.xxxxx.xxx"
serverPort = 7000
transport.tls.certFile = "/certs/fullchain.cer"
transport.tls.keyFile = "/certs/xxxxx.xxx.key"
loginFailExit = false

proxies
name = "egt4"
type = "https"
localIP = "127.0.0.1"
localPort = 20080
customDomains = ["{{.Envs.HOSTNAME}}.cloud.xxxxx.xxx"]

proxies
name = "egt4_ssh"
type = "https"
localIP = "127.0.0.1"
localPort = 4433
customDomains = ["{{.Envs.HOSTNAME}}_ssh.cloud.xxxxx.xxx"]
`

Server config =

`
bindPort = 7000
vhostHTTPSPort = 4433

webServer.addr = "0.0.0.0"
webServer.port = 7500
webServer.user = "xxxxxxx"
webServer.password = "xxxxxxx"
webServer.tls.certFile = "/home/ec2-user/.acme.sh/xxxxx.xxx_ecc/fullchain.cer"
webServer.tls.keyFile = "/home/ec2-user/.acme.sh/xxxxx.xxx_ecc/xxxxx.xxx.key"
`

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @IanAber on GitHub (May 3, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4781 ### Bug Description I am running the server on a Lightsail instance with Amazon Linux 2023 on AMD64 hardware with a client running the latest 64 bit Bookwork Linux on a Raspberry Pi. When trying to connect to the https WEB site in Chrome from a Mac I get... ERR_SSL_UNRECOGNIZED_NAME_ALERT If I use an AMD64 linux client everything works perfectly. It is just the ARM64 Raspberry Pi that returns this error. I do not see anything in the logs at either end, client or server. What should I look for to troubleshoot this? ### frpc Version 0.62.1 ### frps Version 0.62.1 ### System Architecture linux/amd64 server ; linux/ARM64 client ### Configurations ### Client config = ` serverAddr = "cloud.xxxxx.xxx" serverPort = 7000 transport.tls.certFile = "/certs/fullchain.cer" transport.tls.keyFile = "/certs/xxxxx.xxx.key" loginFailExit = false [[proxies]] name = "egt4" type = "https" localIP = "127.0.0.1" localPort = 20080 customDomains = ["{{.Envs.HOSTNAME}}.cloud.xxxxx.xxx"] [[proxies]] name = "egt4_ssh" type = "https" localIP = "127.0.0.1" localPort = 4433 customDomains = ["{{.Envs.HOSTNAME}}_ssh.cloud.xxxxx.xxx"] ` ### Server config = ` bindPort = 7000 vhostHTTPSPort = 4433 webServer.addr = "0.0.0.0" webServer.port = 7500 webServer.user = "xxxxxxx" webServer.password = "xxxxxxx" webServer.tls.certFile = "/home/ec2-user/.acme.sh/xxxxx.xxx_ecc/fullchain.cer" webServer.tls.keyFile = "/home/ec2-user/.acme.sh/xxxxx.xxx_ecc/xxxxx.xxx.key" ` ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror closed this issue

2026-05-05 14:25:06 -06:00

gitea-mirror commented

2026-05-05 14:25:08 -06:00

Author

Owner

Copy link

@IanAber commented on GitHub (May 3, 2025):

Looks like the problem was the host name. The raspberry pi was not setting the HOSTNAME environment variable.

I found this by examining the WEB site at 7500 and seeing the full url listed.

@IanAber commented on GitHub (May 3, 2025): Looks like the problem was the host name. The raspberry pi was not setting the HOSTNAME environment variable. I found this by examining the WEB site at 7500 and seeing the full url listed.

gitea-mirror referenced this issue

2026-05-05 14:49:29 -06:00

[PR #3773] [MERGED] Strict configuration parsing #4828

gitea-mirror referenced this issue

2026-05-05 14:49:51 -06:00

[PR #3845] [MERGED] bump version to v0.53.0 #4845

No Branch/Tag specified