# Help request for Reverse proxy setup with HTTPS to build a server for multiple services

**URL:** <https://dietpi.com/forum/t/help-request-for-reverse-proxy-setup-with-https-to-build-a-server-for-multiple-services/4942>\
**Category:** Troubleshooting\
**Created:** [6 February 2021 14:38 UTC](https://dietpi.com/forum/t/help-request-for-reverse-proxy-setup-with-https-to-build-a-server-for-multiple-services/4942 "2021-02-06T14:38:55Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [7 February 2021 18:19 UTC](https://dietpi.com/forum/t/help-request-for-reverse-proxy-setup-with-https-to-build-a-server-for-multiple-services/4942/21 "2021-02-07T18:19:48Z")

</div>

I don’t think it’s needed to adopt the configuration from Jellyfin website. I did a test and it was quite simple to reach Jellyfin from outside world

create a host [jelly.mydomain.com](http://jelly.mydomain.com)  
forward to my Jellyfin server using it’s local network address and port  
activated SSL certificate + force SSL  
done

 ![picture.PNG](https://dietpi.com/forum/uploads/default/original/2X/c/c92de619580bec086a34aeb9d81270ac7385eb46.png)  
and now Jellyfin is reachable on mobile network

 ![Screenshot_20210207-190925.png](https://dietpi.com/forum/uploads/default/original/2X/c/ca030ca1a520be4eed90cf93b79e11493ad5fab0.png)

---

_[View the full topic](https://dietpi.com/forum/t/help-request-for-reverse-proxy-setup-with-https-to-build-a-server-for-multiple-services/4942)._