Hi
I'm currently relying on synology reverse DNS using mydomain.synology.me , I bought a new domain ie mydomain.com
Currently I'm looking for a way to do a wild card redirect to keep my existing URLs functioning.
so service1.mydomain.synology.me/home should be redirected to service1.mydomain.com/home
Is there a way to implement this on pangolin?
Originally created by @Greso665 on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/774
Hi
I'm currently relying on synology reverse DNS using mydomain.synology.me , I bought a new domain ie mydomain.com
Currently I'm looking for a way to do a wild card redirect to keep my existing URLs functioning.
so **service1.mydomain.synology.me/home** should be redirected to **service1.mydomain.com/home**
Is there a way to implement this on pangolin?
@oschwartz10612 commented on GitHub (May 24, 2025):
I think if I understand you correctly you have Pangolin on the new domain mydomain.com but synology controls the old domain? If thats right you will need to figure out on the synology side I think how to redirect to the new domain because pangolin cant control that. If I misunderstood let me know!
<!-- gh-comment-id:2906352517 -->
@oschwartz10612 commented on GitHub (May 24, 2025):
I think if I understand you correctly you have Pangolin on the new domain `mydomain.com` but synology controls the old domain? If thats right you will need to figure out on the synology side I think how to redirect to the new domain because pangolin cant control that. If I misunderstood let me know!
Previously I forwarded ports 80 and 443 to synology, and it took care of the reverse proxy for my whole homelab
Now since I installed pangolin, all traffic will be sent to pangolin
I configured mydomain.com and it works like a charm, my issue is for the old ones that has synology.me pangolin doesn't recognize this domain.
So I aim to have a wildcard redirections to cover all services, for example:
immich.mydomain.synology.me → immich.mydomain.com
nextcloud.mydomain.synology.me → nextcloud.mydomain.com
Hope this explains.
<!-- gh-comment-id:2906785687 -->
@Greso665 commented on GitHub (May 24, 2025):
Previously I forwarded ports 80 and 443 to synology, and it took care of the reverse proxy for my whole homelab
Now since I installed pangolin, all traffic will be sent to pangolin
I configured mydomain.com and it works like a charm, my issue is for the old ones that has synology.me pangolin doesn't recognize this domain.
So I aim to have a wildcard redirections to cover all services, for example:
immich.mydomain.synology.me → immich.mydomain.com
nextcloud.mydomain.synology.me → nextcloud.mydomain.com
Hope this explains.
@oschwartz10612 commented on GitHub (May 27, 2025):
Yes thank you.
I think this is tricky because immich.mydomain.synology.me still goes to your old instance and does not touch pangolin, so there is nothing we can do in pangolin to make it redirect. You would need to update that endpoint immich.mydomain.synology.me to go to some lightweight http server like nginx I think and then have it redirect to pangolin. Does that make sense? Maybe this guide might help? https://stackoverflow.com/questions/6045020/how-to-redirect-to-a-different-domain-using-nginx
<!-- gh-comment-id:2912827822 -->
@oschwartz10612 commented on GitHub (May 27, 2025):
Yes thank you.
I think this is tricky because `immich.mydomain.synology.me` still goes to your old instance and does not touch pangolin, so there is nothing we can do in pangolin to make it redirect. You would need to update that endpoint `immich.mydomain.synology.me` to go to some lightweight http server like nginx I think and then have it redirect to pangolin. Does that make sense? Maybe this guide might help? https://stackoverflow.com/questions/6045020/how-to-redirect-to-a-different-domain-using-nginx
@github-actions[bot] commented on GitHub (Jun 11, 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:2960879832 -->
@github-actions[bot] commented on GitHub (Jun 11, 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 (Jun 25, 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:3002234661 -->
@github-actions[bot] commented on GitHub (Jun 25, 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.
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 @Greso665 on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/774
Hi
I'm currently relying on synology reverse DNS using mydomain.synology.me , I bought a new domain ie mydomain.com
Currently I'm looking for a way to do a wild card redirect to keep my existing URLs functioning.
so service1.mydomain.synology.me/home should be redirected to service1.mydomain.com/home
Is there a way to implement this on pangolin?
@oschwartz10612 commented on GitHub (May 24, 2025):
I think if I understand you correctly you have Pangolin on the new domain
mydomain.combut synology controls the old domain? If thats right you will need to figure out on the synology side I think how to redirect to the new domain because pangolin cant control that. If I misunderstood let me know!@Greso665 commented on GitHub (May 24, 2025):
Previously I forwarded ports 80 and 443 to synology, and it took care of the reverse proxy for my whole homelab
Now since I installed pangolin, all traffic will be sent to pangolin
I configured mydomain.com and it works like a charm, my issue is for the old ones that has synology.me pangolin doesn't recognize this domain.
So I aim to have a wildcard redirections to cover all services, for example:
immich.mydomain.synology.me → immich.mydomain.com
nextcloud.mydomain.synology.me → nextcloud.mydomain.com
Hope this explains.
@oschwartz10612 commented on GitHub (May 27, 2025):
Yes thank you.
I think this is tricky because
immich.mydomain.synology.mestill goes to your old instance and does not touch pangolin, so there is nothing we can do in pangolin to make it redirect. You would need to update that endpointimmich.mydomain.synology.meto go to some lightweight http server like nginx I think and then have it redirect to pangolin. Does that make sense? Maybe this guide might help? https://stackoverflow.com/questions/6045020/how-to-redirect-to-a-different-domain-using-nginx@github-actions[bot] commented on GitHub (Jun 11, 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 (Jun 25, 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.