ASUSTOR - Website Management

Date:

Topic_id:

Subject:

Description:

content:

<h4>COURSE OBJECTIVES</h4>
Upon completion of this course you should be able to:
<ol>
<li>Use a reverse proxy domain to protect the secure connection of multiple NAS.</li>
<li>Use a reverse proxy domain to improve the security of Apps' HTTPS connection.</li>
</ol>
 
<h4>PREREQUISITES</h4>
Course Prerequisites:
<a target="_blank" href="https://www.asustor.com/online/College_topic?topic=324" rel="noopener">NAS 324: Using HTTPS to Secure NAS Communication</a>
Students are expected to have a working knowledge of:
HTTP/HTTPS
 
<h4>OUTLINE</h4>
<a href="#rp1">1. Introducing Reverse Proxies</a>
<a href="#rp2">2. Protecting the Connections of Multiple NAS Devices</a>
<a href="#rp21">2.1 Adding Proxy Domains</a>
<a href="#rp22">2.2 Add Rules to Existing Proxy Domains</a>
<a href="#rp3">3. Upgrading NAS App Security</a>
<a href="#rp31">3.1 Setting Reverse Proxies to work with Jellyfin</a>
<a href="#rp32">3.2 Setting ownCloud to work with Reverse Proxies</a>
<a href="#rp33">3.3 Set up the HTTPS connection of Syncthing</a>
<a href="#rp34">3.4 Setting Nextcloud to work with Reverse Proxies</a>
<a href="#rp35">3.5 Set up the HTTPS connection of Plex Web</a>
<a href="#rp4">4. Editing Proxy Domains and Rules</a>
<a href="#rp41">4.1 Editing or Removing Proxy Domain</a>
<a href="#rp42">4.2 Edit or Remove Proxy Domain Rules</a>
 <hr /> 
<h4><a name="rp1"></a>1. Introducing Reverse Proxies</h4>
Web browsing is becoming more and more secure. Most apps on an ASUSTOR NAS use a web browser for functionality but don’t necessarily support HTTP Secure. Reverse proxy servers help clients provide web information while protecting the security of transmitted data. Reverse proxy servers on an ASUSTOR NAS that has a valid HTTPS certificate protects data transmitted by an external HTTPS connection. ADM 3.5.2 adds reverse proxies as a new feature. Reverse proxy servers are used to implement HTTPS connections on content or web apps that would not otherwise be protected. Set the domain name on the NAS where the reverse proxy server is to be enabled. And apply for a legal certificate, please refer to the setting method: <a target="_blank" href="https://www.asustor.com/online/College_topic?topic=324" rel="noopener">NAS 324: Using HTTPS to Secure NAS Communication</a> 
 
<h4><a name="rp2"></a>2. Protecting the Connections of Multiple NAS Devices</h4>
When you set up multiple NAS in the same local network and want to connect to the NAS using https securely from the outside, turn on ADM and use the reverse proxy server of one of the NAS to protect the secure connection of multiple NAS, It is not necessary to open all NAS to external network and apply for different domain names.
 
<a name="rp21"></a>2.1 Adding Proxy Domains
To use the legal domain of this NAS to log in to the ADM of other NAS with HTTPS, proxy domains will need to be added first.
 
Step 1
<ul>
<li>Click Reverse Proxy in ADM Preferences.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201143415_74254.png" alt="" width="900" height="562" title="" align="" />
 
Step 2
<ul>
<li>Click Add on the reverse proxy page.</li>
<li>Create a new proxy domain and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201143504_37832.png" alt="" width="860" height="515" title="" align="" />
 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201143656_60010.png" alt="" width="600" height="549" title="" align="" />
 
Step 3
<ul>
<li>Enter a name for easy identification of this proxy domain. Example: ASUSTOR NAS ADM</li>
<li>Select HTTPS and the server name.</li>
<li>Enter an unused communication port. Example: 8880</li>
<li>Select a network interface for use.</li>
<li>Enter the path of this proxy domain rule. Example: /as6602t</li>
<li>Enable port forwarding and press Next.</li>
</ul>
Note: If there is only one service in this proxy domain, the path can only keep "/". If you need to add other rules, you can use Edit to add a path for the first rule. 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201143903_63935.png" alt="" width="600" height="548" title="" align="" />
 
Step 4
<ul>
<li>Enter a name to easily identify domain rules.</li>
<li>Select HTTP and enter the LAN IP of the proxy domain. Example: [192.168.xxx.xxx].</li>
<li>Enter the port of the proxy domain. Example: 8000 (ADM HTTP login port).</li>
<li>Enter the path if the proxy domain has a specific path. ADM login does not require a specific path, a slash (/) is enough.</li>
<li>Click Test Connection to verify that the above information of the proxy domain is correct and if the URL needs a redirect path. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201144002_70958.png" alt="" width="600" height="548" title="" align="" />
 
Step 5
<ul>
<li>Confirm whether the information set is correct and click Finish.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201144115_93275.png" alt="" width="600" height="548" title="" align="" />
 
<ul>
<li>Upon completion, you’ll be able to see the information of the proxy domain on the reverse proxy page.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201144456_44120.png" alt="" width="860" height="515" title="" align="" />
 
Step 6
<ul>
<li>Enter your proxy domain into a web browser. The reverse proxy server will lead the connection to http://192.168.xxx.xxx:8000/.</li>
<li>Use the HTTPS URL of this proxy domain from outside to connect to another NAS and log in to ADM. Use the same MyASUSTOR domain name to log in to the original NAS or add the configured port and path to log in to another NAS to make this connection secure under HTTPS with a valid HTTPS certificate. Reverse proxy servers can be used to open ADM and log in to another NAS with HTTPS. After logging in, other services and apps will need to set their own reverse proxy ports in order to use needed services and apps correctly in a secure connection.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201144601_12919.png" alt="" width="600" height="45" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201144722_95915.png" alt="" width="750" height="46" title="" align="" />
 
<a name="rp22"></a>2.2 Add Rules to Existing Proxy Domains
Additional rules may be added to the existing proxy domain in order to use a different path to open another service. These instructions show how to add a reverse proxy rule to log in to the ADM of another NAS in the domain added in the previous chapter.
 
Step 1
<ul>
<li>Click Add on the Reverse Proxy page.</li>
<li>Click Add to add a rule to an existing proxy domain. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145229_71817.png" alt="" width="860" height="515" title="" align="" />
 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145404_23729.png" alt="" width="600" height="548" title="" align="" />
 
Step 2
<ul>
<li>Select the proxy domain where you want to add a rule, for example: [https://yourddns.myasustor.com:8880].</li>
<li>Enter the path of this new rule, for example: /as5304t, click Next.</li>
</ul>
Note: Because this function is to add rules to the existing proxy domain, the domain name and port of the proxy domain cannot be changed during this process, but a different path must be entered. 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145445_49730.png" alt="" width="600" height="548" title="" align="" />
 
Step 3
<ul>
<li>Enter a name to easily identify the domain rule for the reverse proxy. Example: AS5304T.</li>
<li>Select HTTP and enter the LAN IP of the proxy domain. Example: [192.168.xx.xx].</li>
<li>Enter the port of the proxy domain. Example: 8000 (ADM HTTP login port).</li>
<li>Enter the path if the proxy domain has a specific path. ADM login does not require a specific path, a slash (/) is enough.</li>
<li>Click Test Connection to test whether the above information of the proxy domain is successfully connected and whether its URL needs a redirect path. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145516_81771.png" alt="" width="600" height="548" title="" align="" />
 
Step 4
<ul>
<li>Confirm whether the information set is correct and click Finish.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145547_89791.png" alt="" width="600" height="548" title="" align="" />
 
<ul>
<li>Upon completion, information of the proxy domain will be visible on the reverse proxy page.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145617_47361.png" alt="" width="860" height="515" title="" align="" />
 
Step 5
<ul>
<li>For example, inputting this proxy domain according to the image below will cause the reverse proxy [https://yourddns.myasustor.com:8880/as5304t/] to redirect the connection to [http:// 192.168.xx.xx:8000/].</li>
<li>Use the HTTPS URL of this proxy domain from outside to connect to another newly added NAS and log in to ADM.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145643_53356.png" alt="" width="600" height="44" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145740_76022.png" alt="" width="750" height="47" title="" align="" />
 
<h4><a name="rp3"></a>3. Upgrading NAS App Security</h4>
Apps that are unable to use HTTPS in a NAS can use a reverse proxy server to enable remote HTTPS connections. This chapter will introduce several apps that require specific communication ports and cannot directly use the HTTPS certificate installed on the NAS.
 
<a name="rp31"></a>3.1 Setting Reverse Proxies to work with Jellyfin
The Docker version of Jellyfin does not use the default web server of the NAS. A reverse proxy server needs to be configured in order support HTTPS remote connections. After the NAS has applied for a valid HTTPS certificate, you can now use the reverse proxy server to configure Jellyfin HTTPS connection.
 
Step 1
<ul>
<li>Click Add on the reverse proxy page.</li>
<li>Create a new proxy domain and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182006_RP_add_s1.png" alt="" width="900" height="539" title="" align="" />
 
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182126_RP_create_new_rp_s1.png" alt="" width="600" height="548" title="" align="" />
 
Step 2
<ul>
<li>Enter a name for easy identification of this proxy domain. Example: Jellyfin HTTPS</li>
<li>Select HTTPS and the server name. Example: [yourddns.myasustor.com].</li>
<li>Enter an unused port number. It must also be different from the original Jellyfin communication port. Example: 8196</li>
<li>Select a network interface. Select an asterisk for default.</li>
<li>Enter the path of this proxy domain rule, or leave a slash (/). Turn on port forwarding and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182211_RP_create_new_rp_Jellyfin_s1.png" alt="" width="600" height="548" title="" align="" />
 
Step 3
<ul>
<li>Optional: Enter a name to easily identify the domain rule for the reverse proxy.</li>
<li>Select HTTP and enter the LAN IP of the NAS. Example: [192.168.xx.xx].</li>
<li>Enter the port of the proxy domain. Example: 8096 (Jellyfin HTTP port).</li>
<li>If an app of the proxy domain has a specific path, please enter it otherwise enter a slash (/).</li>
<li>Click Test Connection to test whether the above information of the proxy domain is successfully connected and whether its URL needs a redirect path. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182246_RP_create_new_rp_Jellyfin_s2.png" alt="" width="600" height="548" title="" align="" />
 
Step 4
<ul>
<li>Confirm whether the information set is correct and click Finish.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182303_RP_create_new_rp_Jellyfin_s3.png" alt="" width="600" height="548" title="" align="" />
 
<ul>
<li>Upon completion, information of the proxy domain will be visible on the reverse proxy page.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182344_RP_create_new_rp_Jellyfin_s4.png" alt="" width="900" height="539" title="" align="" />
 
Step 5
<ul>
<li>Take this proxy domain as an example, enter [https://yourddns.myasustor.com:8196/] in the web browser, and the reverse proxy server will direct the connection to [http://192.168.xx.xxx:8096/] which is the Jellyfin local URL.</li>
<li>Use the HTTPS URL of this proxy domain from the outside to connect to Jellyfin installed on this NAS and log in.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182408_RP_Chrome_URL_Jellyfin.png" alt="" width="600" height="44" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182431_RP_Firefox_URL_Jellyfin.png" alt="" width="750" height="47" title="" align="" />
 
<a name="rp32"></a>3.2 Setting ownCloud to work with Reverse Proxies
The Docker version of ownCloud does not use the default web server of the NAS. A reverse proxy server needs to be configured in order support HTTPS remote connections. After the NAS has applied for a valid HTTPS certificate, you can now use the reverse proxy server to configure ownCloud HTTPS connection.
 
Step 1
<ul>
<li>Click Add on the reverse proxy page.</li>
<li>Create a new proxy domain and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182006_RP_add_s1.png" alt="" width="900" height="539" title="" align="" />
 
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182126_RP_create_new_rp_s1.png" alt="" width="600" height="548" title="" align="" />
 
Step 2
<ul>
<li>Enter a name for easy identification of this proxy domain. Example: ownCloud HTTPS</li>
<li>Select HTTPS and the server name. Example: [yourddns.myasustor.com].</li>
<li>Enter an unused port number. It must also be different from the original ownCloud communication port. Example: 32882</li>
<li>Select a network interface. Select an asterisk for default.</li>
<li>Enter the path of this proxy domain rule, or leave a slash (/). Turn on port forwarding and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182644_RP_create_new_rp_ownCloud_s1.png" alt="" width="600" height="548" title="" align="" />
 
Step 3
<ul>
<li>Optional: Enter a name to easily identify the domain rule for the reverse proxy.</li>
<li>Select HTTP and enter the LAN IP of the NAS. Example: [192.168.xx.xx].</li>
<li>Enter the port of the proxy domain. Example: 32880 (ownCloud HTTP port).</li>
<li>If an app of the proxy domain has a specific path, please enter it otherwise enter a slash (/).</li>
<li>Click Test Connection to test whether the above information of the proxy domain is successfully connected and whether its URL needs a redirect path. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182702_RP_create_new_rp_ownCloud_s2.png" alt="" width="600" height="548" title="" align="" />
 
Step 4
<ul>
<li>Confirm whether the information set is correct and click Finish.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182719_RP_create_new_rp_ownCloud_s3.png" alt="" width="600" height="548" title="" align="" />
 
<ul>
<li>Upon completion, information of the proxy domain will be visible on the reverse proxy page.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182749_RP_create_new_rp_ownCloud_s4.png" alt="" width="900" height="539" title="" align="" />
 
Step 5
ownCloud has strict restrictions on the domains it can access. When setting up a reverse proxy server for ownCloud, you need to add this domain to ownCloud's "trusted_domains" configuration for normal use.
<ul>
<li>Download /share/Docker/ownCloud/data/config/config.php to your computer, rename the file to "zz-user.config.php" and then open a text editor to edit it.</li>
<li>Only retain the 'trusted_domains' setting in the zz-user.config.php file, and add the NAS's reverse proxy server domain, [ 1 => 'yourddns.myasustor.com', ] to the content and then archive.
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182929_RP_create_new_rp_ownCloud_s51.png" alt="" width="550" height="262" title="" align="" />
</li>
<li>Upload the edited zz-user.config.php to the NAS folder [/share/Docker/ownCloud/data/config/].
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183041_RP_create_new_rp_ownCloud_s5.png" alt="" width="660" height="323" title="" align="" />
</li>
</ul>
 Note: Using ADM 5.0 and above, you can download and install Text Editor from App Central and edit [/share/Docker/ownCloud/data/config/zz-user.config.php] directly in ADM.
 
Step 6
<ul>
<li>Take this proxy domain as an example, enter [https://yourddns.myasustor.com:32882/] in the web browser, and the reverse proxy server will direct the connection to [http://192.168.xx.xxx:32880/] which is the ownCloud local URL.</li>
<li>Use the HTTPS URL of this proxy domain from the outside to connect to ownCloud installed on this NAS and log in.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183106_RP_Chrome_URL_ownCloud.png" alt="" width="600" height="44" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183120_RP_Firefox_URL_ownCloud.png" alt="" width="750" height="47" title="" align="" />
 
<a name="rp33"></a>3.3 Set up the HTTPS connection of Syncthing
The Docker version of Syncthing does not use the default web server of the NAS. A reverse proxy server needs to be configured in order support HTTPS remote connections. After the NAS has applied for a valid HTTPS certificate, you can now use the reverse proxy server to configure Syncthing HTTPS connection.
Note: In this example, an existing proxy domain is used to add rules, and there is no need to set an additional port. Users can also use "Create new proxy domain" and add another port to set up a reverse proxy for Syncthing.
 
Step 1
<ul>
<li>Click Add on the Reverse Proxy page.</li>
<li>Click Add to add a rule to an existing proxy domain. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102182006_RP_add_s1.png" alt="" width="900" height="539" title="" align="" />
 
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183146_RP_add_new_rule_rp_s1.png" alt="" width="600" height="548" title="" align="" />
 
Step 2
<ul>
<li>Select the proxy domain where you want to add a rule, for example: [https://yourddns.myasustor.com:18862].</li>
<li>Enter the path of this new rule, for example: /syncthing, click Next.</li>
</ul>
Note: Because this function is to add rules to the existing proxy domain, the domain name and port of the proxy domain cannot be changed during this process, but a different path must be entered. 
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183217_RP_add_new_rule_Syncthing_s1.png" alt="" width="600" height="548" title="" align="" />
 
Step 3
<ul>
<li>Enter a name for easy identification of this proxy domain. Example: Syncthing</li>
<li>Select HTTP and enter the LAN IP of the NAS. Example: [192.168.xx.xxx].</li>
<li>Enter the port of the proxy domain. Example: 28384 (Syncthing HTTP port).</li>
<li>If an app of the proxy domain has a specific path, please enter it otherwise enter a slash (/).</li>
<li>Click Test Connection to test whether the above information of the proxy domain is successfully connected and whether its URL needs a redirect path. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183302_RP_create_new_rp_Syncthing_s2.png" alt="" width="600" height="548" title="" align="" />
 
Step 4
<ul>
<li>Confirm whether the information set is correct and click Finish.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183327_RP_create_new_rp_Syncthing_s3.png" alt="" width="600" height="548" title="" align="" />
 
<ul>
<li>Upon completion, information of the proxy domain will be visible on the reverse proxy page.</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183345_RP_create_new_rp_Syncthing_s4.png" alt="" width="900" height="539" title="" align="" />
 
Step 5
<ul>
<li>Take this proxy domain as an example, enter [https://yourddns.myasustor.com:18862/syncthing/] in the web browser, and the reverse proxy server will lead the connection to [http://192.168.xx.xxx:28384/] which is the Syncthing local URL.</li>
<li>Use the HTTPS URL of this proxy domain from the outside to connect to Syncthing installed on this NAS and log in.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183409_RP_Chrome_URL_Syncthing.png" alt="" width="600" height="44" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102183421_RP_Firefox_URL_Syncthing.png" alt="" width="750" height="47" title="" align="" />
 
<a name="rp34"></a>3.4 Setting Nextcloud to work with Reverse Proxies
 A default reverse proxy for Nextcloud has been added on ADM 4.1, users no longer need to configure it themselves if the NAS is updated to ADM 4.1.0 or above. Currently, the default reverse proxy cannot be allowed for users to add a new rule.
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102184636_RP_ADM41_Default_proxy_nextcloud.png" alt="" width="900" height="539" title="" align="" />
 
<ul>
<li>Take this proxy domain as an example, enter [https://yourddns.myasustor.com:8622/nextcloud-docker/] in the web browser, and the reverse proxy server will direct the connection to [http://192.168.xx.xxx:32680/] which is the Nextcloud local URL.</li>
<li>Use the HTTPS URL of this proxy domain from the outside to connect to Nextcloud installed on this NAS and log in.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102184807_RP_Chrome_URL_default_Nextcloud.png" alt="" width="600" height="42" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102184847_RP_Firefox_URL_default_Nextcloud.png" alt="" width="750" height="47" title="" align="" />
 
<div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
<div class="panel panel-default">
<div class="panel-heading" role="tab" id="heading1">
<h4 class="panel-title"><a role="button" data-toggle="collapse" data-parent="#accordion" href="#collapse1" aria-expanded="true" aria-controls="collapse1"> Setting Nextcloud to Work with Reverse Proxies on ADM 4.0 or ADM 3.5:</a></h4>
</div>
<div id="collapse1" class="panel-collapse collapse" role="tabpanel" aria-labelledby="heading1">
<div class="panel-body"> 
The Docker version of Nextcloud does not use the default web server of the NAS. A reverse proxy server needs to be configured in order support HTTPS remote connections. After the NAS has applied for a valid HTTPS certificate, you can now use the reverse proxy server to configure Nextcloud HTTPS connection.
 
Step 1
<ul>
<li>Click Add on the reverse proxy page.</li>
<li>Create a new proxy domain and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145229_71817.png" alt="" width="860" height="515" title="" align="" />
 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201150705_21542.png" alt="" width="600" height="548" title="" align="" />
 
Step 2
<ul>
<li>Enter a name for easy identification of this proxy domain. Example: Nextcloud HTTPS</li>
<li>Select HTTPS and the server name. Example: [yourddns.myasustor.com].</li>
<li>Enter an unused port number. It must also be different from the original Nextcloud communication port. Example: 32681</li>
<li>Select a network interface. Select an asterisk for default.</li>
<li>Enter the path of this proxy domain rule, or leave a slash (/). Turn on port forwarding and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201151234_54468.png" alt="" width="600" height="548" title="" align="" />
 
Step 3
<ul>
<li>Optional: Enter a name to easily identify the domain rule for the reverse proxy.</li>
<li>Select HTTP and enter the LAN IP of the NAS. Example: [192.168.xx.xx].</li>
<li>Enter the port of the proxy domain. Example: 32680 (Nextcloud HTTP port).</li>
<li>If an app of the proxy domain has a specific path, please enter it otherwise enter a slash (/).</li>
<li>Click Test Connection to test whether the above information of the proxy domain is successfully connected and whether its URL needs a redirect path. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201151621_31523.png" alt="" width="600" height="548" title="" align="" />
 
Step 4
<ul>
<li>Confirm whether the information set is correct and click Finish.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201151651_67026.png" alt="" width="600" height="548" title="" align="" />
 
<ul>
<li>Upon completion, information of the proxy domain will be visible on the reverse proxy page.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201151716_33890.png" alt="" width="860" height="515" title="" align="" />
 
Step 5
Nextcloud has strict restrictions on the domains it can access. The Nextcloud document explains that when setting up a reverse proxy server, you’ll need to add other settings to Nextcloud's config.php for normal use. For details, please refer to <a target="_blank" href="https://docs.nextcloud.com/server/20/admin_manual/configuration_server/reverse_proxy_configuration.html" rel="noopener">Nextcloud documentation</a>.
<ul>
<li>Download /volume1/Docker/Nextcloud/config/config.php to your computer and open a text editor to edit it.</li>
<li>Add ['overwritehost' =>'yourddns.myasustor.com:32681',] and ['overwriteprotocol' =>'https',] below the content of the config.php file and archive.</li>
<li>Upload the edited config.php to the NAS folder [/volume1/Docker/Nextcloud/config] to overwrite the original file.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201151742_27317.png" alt="" width="600" height="49" title="" align="" />
 
Step 6
<ul>
<li>Take this proxy domain as an example, enter [https://yourddns.myasustor.com:32681/] in the web browser, and the reverse proxy server will direct the connection to [http://192.168.xx.xxx:32680/] which is the Nextcloud local URL.</li>
<li>Use the HTTPS URL of this proxy domain from the outside to connect to Nextcloud installed on this NAS and log in.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201151853_86966.png" alt="" width="600" height="44" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201151917_73916.png" alt="" width="750" height="47" title="" align="" />
</div>
</div>
</div>
</div>
 
<a name="rp35"></a>3.5 Set up the HTTPS connection of Plex Web
 A default reverse proxy for Plex Media Server has been added on ADM 4.1, users no longer need to configure it themselves if the NAS is updated to ADM 4.1.0 or above. Currently, the default reverse proxy cannot be allowed for users to add a new rule.
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102184937_RP_ADM41_Default_proxy_plex.png" alt="" width="900" height="539" title="" align="" />
 
<ul>
<li>Take this proxy domain as an example, enter [https://yourddns.myasustor.com:8622/plexmediaserver/] in the web browser, and the reverse proxy server will direct the connection to [https://192.168.xx.xxx:32400/] which is the Plex Media Server local URL.</li>
<li>Use the HTTPS URL of this proxy domain from the outside to connect to Plex Media Server installed on this NAS and log in.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102185051_RP_Chrome_URL_default_Plex.png" alt="" width="600" height="42" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/tinymce/upload_img_20231102185114_RP_Firefox_URL_default_Plex.png" alt="" width="750" height="47" title="" align="" />
 
<div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
<div class="panel panel-default">
<div class="panel-heading" role="tab" id="heading2">
<h4 class="panel-title"><a role="button" data-toggle="collapse" data-parent="#accordion" href="#collapse2" aria-expanded="true" aria-controls="collapse2"> Set up the HTTPS connection of Plex Web on ADM 4.0 or ADM 3.5:</a></h4>
</div>
<div id="collapse2" class="panel-collapse collapse" role="tabpanel" aria-labelledby="heading2">
<div class="panel-body"> 
With Plex Media Server installed on a NAS, directly use a web browser to open Plex to manage media libraries as well as play audio and video files. The HTTPS certificate bound to the NAS is for the NAS IP. The Dynamic DNS in an ASUSTOR NAS cannot be used to open Plex securely. Use reverse proxy server to open Plex using the DDNS with an HTTPS connection.
Before setting a reverse proxy domain, you’ll need to open Plex with HTTPS and log in to your Plex account. For Plex Media Server installation and media library settings, please refer to: <a target="_blank" href="https://www.asustor.com/online/College_topic?topic=235" rel="noopener">NAS 235: Introducing Plex Media Server</a>
 
Step 1
<ul>
<li>On the ADM desktop, click Plex Media Server.</li>
<li>In the address bar of the browser, change the web page protocol of Plex Web to HTTPS. Example: https://192.168.xx.xxx:32400</li>
<li>Log in to your registered Plex account, and allow HTTPS connections from this IP.</li>
<li>Confirm that Plex can display media libraries and play content.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152238_37379.png" alt="" width="900" height="506" title="" align="" />
 
Step 2
<ul>
<li>Click Add on the reverse proxy page.</li>
<li>Create a new proxy domain and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201145229_71817.png" alt="" width="860" height="515" title="" align="" />
 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201150705_21542.png" alt="" width="600" height="548" title="" align="" />
 
Step 3
<ul>
<li>Enter a name for easy identification of this proxy domain. Example: Plex HTTPS</li>
<li>Select HTTPS and the server name. Example: [yourddns.myasustor.com].</li>
<li>Enter an unused port number. It must also be different from the original Plex communication port. Example: 32411</li>
<li>Select a network interface. Select an asterisk for default.</li>
<li>Enter the path of this proxy domain rule, or leave a slash (/). Turn on port forwarding and click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152347_88290.png" alt="" width="600" height="548" title="" align="" />
 
Step 4
<ul>
<li>Optional: Enter a name to easily identify the domain rule for the reverse proxy.</li>
<li>Select HTTPS and enter the LAN IP of the NAS. Example: [192.168.xx.xx].</li>
<li>Enter the port of the proxy domain. Example: 32400 (Plex HTTP/HTTPS port).</li>
<li>If an app of the proxy domain has a specific path, please enter it, otherwise enter a slash (/).</li>
<li>Click Test Connection to test whether the above information of the proxy domain is successfully connected and whether its URL needs a redirect path. Click Next.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152421_11691.png" alt="" width="600" height="548" title="" align="" />
 
Step 5
<ul>
<li>Confirm whether the information set is correct and click Finish.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152450_66744.png" alt="" width="600" height="548" title="" align="" />
 
<ul>
<li>Upon completion, information of the proxy domain will be visible on the reverse proxy page.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152520_29785.png" alt="" width="860" height="515" title="" align="" />
 
Step 6
<ul>
<li>Take this proxy domain as an example, enter [https://yourddns.myasustor.com:32411/] in the web browser, and the reverse proxy server will direct the connection to [https://192.168.xx.xxx:32400/] which is the Plex Media Server local URL.</li>
<li>Use the HTTPS URL of this proxy domain from the outside to connect to Plex Media Server installed on this NAS and log in.</li>
</ul>
 
 On Chrome:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152549_58261.png" alt="" width="600" height="44" title="" align="" />
 
 On Firefox:
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152615_77083.png" alt="" width="750" height="47" title="" align="" />
</div>
</div>
</div>
</div>
 
<h4><a name="rp4"></a>4. Editing Proxy Domains and Rules</h4>
 
<a name="rp41"></a>4.1 Editing or Removing Proxy Domains
<ul>
<li>After selecting a proxy domain, click Edit to edit the name, network protocol, server name and/or port of the reverse proxy domain. After editing a proxy domain, all the rules in that proxy domain will be revised accordingly.</li>
<li>Click Remove to delete a proxy domain and the rules below.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152805_65377.png" alt="" width="860" height="515" title="" align="" />
 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201152835_68366.png" alt="" width="660" height="520" title="" align="" />
 
<a id="rp42"></a>4.2 Edit or Remove Proxy Domain Rules
<ul>
<li>On the Reverse Proxy page, click on a proxy domain to expand the rules of the proxy domain. After selecting a rule, click Edit to edit the network protocol of the reverse proxy domain on the proxy domain page. You can edit the name, network protocol, host name, port and path of the rule as well as enable or disable the proxy domain rules on this page.</li>
<li>Click Remove to delete this proxy domain rule, and deleting the last rule will remove its proxy domain.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201153004_54735.png" alt="" width="860" height="515" title="" align="" />
 
<ul>
<li>If you need to temporarily disable a reverse proxy connection, you can disable the reverse proxy domain rule on the edit rules page instead of removing the temporarily disabled rule.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201153228_94955.png" alt="" width="660" height="519" title="" align="" />
 
<img src="https://www.asustor.com/images/kindeditor/image/20201201/20201201153300_22724.png" alt="" width="860" height="515" title="" align="" />
 <hr />
<h3>Learn More</h3>
<iframe width="560" height="315" src="https://www.youtube.com/embed/QDugezceyYk?si=AvRI1igVsKu_X-IV" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen="allowfullscreen"></iframe>

Publish: