First, thank you for this great product. I was doing a highly complicated configuration to do what exactly Pangolin does.
Second, I have an issue when it comes to the encryption of a website. I get this warning from Google Chrome this warning. [Not secure] and by the way, this one has already been running for about 15 days, and there is nothing in the logs
Pangolin v1.5.1
Originally created by @Nick390 on GitHub (Jun 14, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/912
First, thank you for this great product. I was doing a highly complicated configuration to do what exactly Pangolin does.
Second, I have an issue when it comes to the encryption of a website. I get this warning from Google Chrome this warning. [Not secure] and by the way, this one has already been running for about 15 days, and there is nothing in the logs
Pangolin v1.5.1
Are you transferring services or manually adding DNS rules? I had this issue when I set up a service before DNS had updated. Try turning off SSL, saving, turning SSL back on, and saving again.
<!-- gh-comment-id:2972855067 -->
@Trainmaster2 commented on GitHub (Jun 14, 2025):
Are you transferring services or manually adding DNS rules? I had this issue when I set up a service before DNS had updated. Try turning off SSL, saving, turning SSL back on, and saving again.
@oschwartz10612 commented on GitHub (Jun 15, 2025):
Did you say it was working fine and then stopped working? Or is this the first time you are making this resource?
Could you try restarting Traefik and/or taking a look at the logs to see if there are any issues with certificate generation? My guess is it might be using a self signed cert.
<!-- gh-comment-id:2974171935 -->
@oschwartz10612 commented on GitHub (Jun 15, 2025):
Did you say it was working fine and then stopped working? Or is this the first time you are making this resource?
Could you try restarting Traefik and/or taking a look at the logs to see if there are any issues with certificate generation? My guess is it might be using a self signed cert.
@github-actions[bot] commented on GitHub (Jun 30, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3017344827 -->
@github-actions[bot] commented on GitHub (Jun 30, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Jul 14, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
<!-- gh-comment-id:3067434546 -->
@github-actions[bot] commented on GitHub (Jul 14, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
I have deleted the resource then add it again and I have used uptime kuma to monitor the certification and I will keep you updated if there is something in the future currently everything works fine.
<!-- gh-comment-id:3130409250 -->
@Nick390 commented on GitHub (Jul 29, 2025):
I have deleted the resource then add it again and I have used uptime kuma to monitor the certification and I will keep you updated if there is something in the future currently everything works fine.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Nick390 on GitHub (Jun 14, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/912
First, thank you for this great product. I was doing a highly complicated configuration to do what exactly Pangolin does.
Second, I have an issue when it comes to the encryption of a website. I get this warning from Google Chrome this warning. [Not secure] and by the way, this one has already been running for about 15 days, and there is nothing in the logs
Pangolin v1.5.1
@Trainmaster2 commented on GitHub (Jun 14, 2025):
Are you transferring services or manually adding DNS rules? I had this issue when I set up a service before DNS had updated. Try turning off SSL, saving, turning SSL back on, and saving again.
@Nick390 commented on GitHub (Jun 14, 2025):
I added A Record and directed it to the server then added the service.
@oschwartz10612 commented on GitHub (Jun 15, 2025):
Did you say it was working fine and then stopped working? Or is this the first time you are making this resource?
Could you try restarting Traefik and/or taking a look at the logs to see if there are any issues with certificate generation? My guess is it might be using a self signed cert.
@github-actions[bot] commented on GitHub (Jun 30, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Jul 14, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
@Nick390 commented on GitHub (Jul 29, 2025):
I have deleted the resource then add it again and I have used uptime kuma to monitor the certification and I will keep you updated if there is something in the future currently everything works fine.