You have 30 minutes to complete this form before the CAPTCHA will expire.

Security image * Required field
This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param=&quot;Host a Jitsi Meet Server&quot;]427[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by Filip<br /><br /><comcode-quote param="287">I have made a installation on a rpi4 &nbsp;that was already running with a nginx in a ispconfig setup and the installation was easy following the guide/video.<br /><br />But I did have rocket chat and alot of other stuff installed on my small the rpi4 computer and the jisti modified my nginx.conf so I think I will change the setup so &nbsp;<br />the jitsi meet is running on a standalone rpi4 computer but this also need some type of proxy/forward solution on the ispconfing/nginx on 192.168.0.5 (need forward) to 192.168.0.6<br />on router i do portforward on wan 80,443 tcp and &nbsp;UDP/10000 to 192.168.0.5 but I think the LTE needs the port 80 when making the certificate (not sure if I can avoid it and use other ports here) because if I did port forward to the rpi4 on 192.168.0.6 no problem so maybe running jisti on 192.168.0.6:4443 would be a solution for more easy installation but I think LTE needed a response/answer on port 80 &nbsp;I am not really sure ?<br /><br />I have wan/firewallrouter&mdash;-&gt;switch<br />&mdash;&gt;rpi4192.168.0.5(ispconfig normal ports 80,443,8080 etc)<br />&mdash;&gt;rpi4192.168.0.6(jistsi) solution maybe to use 4443 here and do portforward but maybe a problem with port 80 doing LTE <br /><br />Any suggestions?<br />&nbsp;&nbsp;&nbsp;A little complicated to explain but running ispconfing on the rpi4 on ubuntu18.04 is nice but running jiste on the same rpi4 is to much and the<br />numbers of users capasity is surely limitd by the power of the rpi4 but only a few users is fine for now <img class="top_vertical_alignment" alt=";)" src="https://nerdonthestreet.com/themes/default/images/cns_emoticons/wink.png" /><br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color [Font] Arial Courier Georgia Impact Times Trebuchet Verdana Tahoma Geneva Helvetica [Size] 0.8 1 1.5 2 2.5 3 4 [Color] Black Blue Gray Green Orange Purple Red White Yellow This is a reported post for a post in the topic [post param="Host a Jitsi Meet Server"]427[/post], by Filip [quote="287"] I have made a installation on a rpi4 that was already running with a nginx in a ispconfig setup and the installation was easy following the guide/video. But I did have rocket chat and alot of other stuff installed on my small the rpi4 computer and the jisti modified my nginx.conf so I think I will change the setup so the jitsi meet is running on a standalone rpi4 computer but this also need some type of proxy/forward solution on the ispconfing/nginx on 192.168.0.5 (need forward) to 192.168.0.6 on router i do portforward on wan 80,443 tcp and UDP/10000 to 192.168.0.5 but I think the LTE needs the port 80 when making the certificate (not sure if I can avoid it and use other ports here) because if I did port forward to the rpi4 on 192.168.0.6 no problem so maybe running jisti on 192.168.0.6:4443 would be a solution for more easy installation but I think LTE needed a response/answer on port 80 I am not really sure ? I have wan/firewallrouter---->switch --->rpi4192.168.0.5(ispconfig normal ports 80,443,8080 etc) --->rpi4192.168.0.6(jistsi) solution maybe to use 4443 here and do portforward but maybe a problem with port 80 doing LTE Any suggestions? A little complicated to explain but running ispconfing on the rpi4 on ubuntu18.04 is nice but running jiste on the same rpi4 is to much and the numbers of users capasity is surely limitd by the power of the rpi4 but only a few users is fine for now ;) [/quote] //// PUT YOUR REPORT BELOW \\\\ View all Use of this website implies that you agree to the website rules and privacy policy.