Accessing a local Jitsi Meet domain

Discussion in 'Installation/Configuration' started by Michel-André, Aug 20, 2025.

Tags:
  1. Michel-André

    Michel-André New Member

    Salut to all,

    On my internet firewall/router,
    i- I redirected port 443/80 to the IP of ISPconfig running on my LOCAL LAN.
    - I redirected port 8007 to the IP of Proxmox Backup Server running on my LOCAL LAN.
    - I redirected port 8006 to the IP of Proxmox Virtual Environment running on my LOCAL LAN.

    - I have 3 different WordPress domains hosted by ISPconfig running on my LOCAL LAN.
    - In ISPconfig, using the DNS wizard, I created DNS records for all those domains and also for PBS and PVE.

    From the internet, I can access all my WordPress domains hosted by ISPconfig with no problem.
    From the internet, I can access Proxmox Backup Server running on my LOCAL LAN on port 8007 with no problem.
    From the internet, I can access Proxmox Virtual Environment running on my LOCAL LAN on port 8006 with no problem.

    From the internet, I would like to access a LOCAL domain not hosted by ISPconfig. This domain is also using port 443/80.
    QUESTION:
    How can I do this?

    Any suggestion appreciated,

    Michel-André
     
    Michel-André, Aug 20, 2025
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Add the domain to ISPConfig as a website, then create a proxy config in the apache or nginx directives of the website to proxy the traffic from that domain to your other website that you host on another server. You will probably have to use the local ip address of that other server as proxy target.
     
    till, Aug 20, 2025
    #2
  3. Michel-André

    Michel-André New Member

    Salut Till,

    Thank you for your answer.
    I will test that soon and let you know,

    Michel-André
     
    Michel-André, Aug 20, 2025
    #3
  4. Michel-André

    Michel-André New Member

    Salut Till,

    On ISPconfig, I did a brand new default installation of a web site with the same domain name as the real destination.tld and using the IP of ISPconfig.
    I used all the same parameters as another working web site hosted by ISPconfig. Only the domain name is different.
    I have a Let's Encrypt certificate for the domain destination.tld hosted by ISPconfig.

    On the same Local LAN, on a station I have the Preferred DNS server pointing to the IP of ISPconfig.
    I cleared the caches of the station and the browser.
    This station can access destination.tld hosted by ISPconfig with no problem at all.

    Questions:
    1) Up to now and before trying redirection, I did correctly or am I missing something for the configuration of destination.tld hosted by ISPconfig?
    2) On the ISPconfig DNS page for destination.tld hosted by ISPconfig, is it correct to use the IP of the ISPconfig or do I have to use the real Local IP of destination.tld?

    Any suggestion appreciated,

    Michel-André
     
    Last edited: Aug 24, 2025
    Michel-André, Aug 24, 2025
    #4
  5. Michel-André

    Michel-André New Member

    Salut to all!

    #### ISPCONFIG DOMAINS CONFIGURATION DIFFERENCES
    ### working-domains hosted on ISPconfig
    ## DNS BUTTON
    # Records
    A: 192.168.72.121
    ## Sites BUTTON
    # Domain TAB
    Auto-Subdomain: www.
    # Redirect TAB
    SEO Redirect: *.domain.tld => www.domain.tld

    ### destination.tld hosted on ISPconfig
    ## DNS BUTTON
    # Records
    A: 192.168.72.170
    ## Sites BUTTON
    # Domain TAB
    Auto-Subdomain: None
    # Redirect TAB
    SEO Redirect: * => domain.tld

    Testing access from Local LAN and from the Internet:
    - From a station on LOCAL LAN, I can access both working-domains hosted on ISPconfig and the page of the real destination.tld.
    - From the INTERNET, with the firewall redirecting ports 80/443 to the IP of ISPCONFIG; I can access only the working-domains hosted on ISPconfig and cannot access the page of the real destination.tld.
    - From the INTERNET, with the firewall redirecting ports 80/443 to the IP of DESTINATION.TLD, I can access only the page of the real destination.tld and cannot access the pages of working-domains hosted on ISPconfig.

    I've done a lot of googling and over a hundred tests and I'm almost there...

    CONCLUSION:
    1) The firewall is working correctly.
    2) ISPconfig is working correctly for requests from Local LAN but doesn't redirect from the internet.

    QUESTION:
    What are the complete and exact PHP directives for the redirection to the real destination.tld.

    Any suggestions will be greatly appreciated.

    Michel-André
     
    Michel-André, Aug 25, 2025
    #5
  6. Michel-André

    Michel-André New Member

    Salut to all!

    I've changed the title of this post and added a network diagram to increase the chances that someone can provide the informations I need to get Jitsi Meet working properly.

    [​IMG]


    If anyone can provide the informations I need to resolve this issue, I promise to write a step-by-step guide so even a newbie can install a complete and working Jitsi Meet alongside ISPconfig.

    Michel-André
     
    Michel-André, Aug 26, 2025
    #6
  7. Michel-André

    Michel-André New Member

    1,383 people read this post.
    No one provided the exact PHP directives for ISPconfig to redirect a port 443 request from the Internet to a domain on the Local LAN.

    Conclusion:
    ISPCONFIG CANNOT REDIRECT a port 443 request from the Internet to a domain on the Local LAN.

    PROVE ME WRONG!

    Michel-André
     
    Michel-André, Sep 1, 2025
    #7
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    There are several threads in this forum on how to set up a proxy; simply use the search function. Or you read the Apache or Nginx documentation.

    If you do not have the knowledge to do it and do not want to use the search function and read threads that describe what to add to Apache or Nginx directives, then contact business support and ask them for help. However, note that business support is not free: https://www.ispconfig.org/get-support/?type=ispconfig
     
    till, Sep 1, 2025
    #8
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Btw. Here is an example of a reverse proxy config if ISPConfig uses Apache:

    Code:
    ProxyPass /.well-known/acme-challenge/ !
ProxyPass / http://1.2.3.4:8000/
ProxyPassReverse / http://1.2.3.4:8000/
    I did not modify the example I had lying around to any specific IP or port for your configuration, so you have to adjust this for your setup.
     
    till, Sep 1, 2025
    #9
  10. Michel-André

    Michel-André New Member

    My small knowledge may not be as complete as your omniscient person's, but at least I read a post and its replies completely before commenting.
    Regarding your last comment, which I already tried and it didn't work, at least I know it's always better to use HTTPS instead of HTTP; especially if you have to provide a password....

    The best thread I found on your forums is:
    https://forum.howtoforge.com/threads/reverse-proxy-with-ispconfig3-apache2.89422/
    Also like him before, I was using a system other than ISPconfig, and the redirections worked perfectly.

    If the ISPconfig redirection works so well, please tell me why this person didn't reply to thank you for your suggestion?

    Give me the URL of a domain managed by ISPconfig and the URL of a working domain on the same Local LAN, and only then, will I start to believe that ISPconfig can redirect a 443 request from the Internet to a local domain.

    I still maintain that:
    Michel-André
     
    Michel-André, Sep 1, 2025
    #10
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    Then do us a favor and go back to that other system.

    Why should he do that? Many users do not express gratitude for the help they receive by pressing the thanks button.

    And you're posting your contact form link there so that someone can contact you and offer to work for you for free? You must be kidding....

    Why do you think it should matter to me what you believe or that I must prove you anything? I know proxy redirects in Apache and Nginx work when entered in Apache or Nginx directives field in ISPConfig, and I have done proxy redirects many times, and tens of thousands of ISPConfig users have done it too. As I mentioned before, if you are unable to configure and maintain your system yourself, feel free to contact Thom from ISPConfig's business support. Here in the community forum, we provide guidance on achieving specific goals, but we do not manage your server for free and we do not pay your support bills.

    You are always free to maintain claiming such nonsense. You probably believe someone from the business support team will start working for free for you and write you a custom config based on the network diagram you posted because of such claims, but this will not be the case. I provided guidance on how to perform a proxy redirect, and you can find more information in many other posts and the Apache documentation on how to do a proxy redirect in Apache. That's not even ISPConfig-specific, as ISPConfig is not responsible for the redirect; it's Apache that handles it. ISPConfig is a hosting control panel, which is a software that writes config files, and not an HTTP server by itself. What ISPConfig does is write the proxy configuration you enter into the Apache directives field into the vhost file.
     
    till, Sep 2, 2025
    #11
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    Also, have you even evaluated what Jitsi Meet requires? A simple question to an AI:

    Result:

    so as you can see, it shows you the same proxy statements I posted for the basic https proxying:
    Code:
    # Web app (jitsi-meet web)
  ProxyPass        / http://127.0.0.1:8080/
  ProxyPassReverse / http://127.0.0.1:8080/
    but also other URL's you need to redirect and some jitsi specific settings:

    Code:
    ProxyPreserveHost On
SSLProxyEngine On
RequestHeader set X-Forwarded-Proto "https"

# Web app (jitsi-meet web)
ProxyPass / http://127.0.0.1:8080/
ProxyPassReverse / http://127.0.0.1:8080/

# XMPP over WebSocket to Prosody
ProxyPass /xmpp-websocket ws://127.0.0.1:5280/xmpp-websocket
ProxyPassReverse /xmpp-websocket ws://127.0.0.1:5280/xmpp-websocket

# (Optional old path) BOSH
ProxyPass /http-bind http://127.0.0.1:5280/http-bind
ProxyPassReverse /http-bind http://127.0.0.1:5280/http-bind

# Colibri (JVB) WebSocket for stats/ICE (newer JVBs expose this)
ProxyPass /colibri-ws/ ws://127.0.0.1:9090/colibri-ws/
ProxyPassReverse /colibri-ws/ ws://127.0.0.1:9090/colibri-ws/
     
    till, Sep 2, 2025
    #12

Share This Page