Jump to content

Raz

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Raz

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you buy your domain, you have to change the dns records to point it to your public ip. So something like "sonarr.mydomain.com" points to "yourpublicip" and on nginx proxy manager you setup everything according to your configurations
  2. Don't you have a domain name? You still need a domain name! If you don't have it, you have to use Duck DNS
  3. If you don't have a static public IP, you need something like DuckDNS point your domain/subdomains to your unRaid Server
  4. Are you talking about host ports or container ports? I have an nginx proxy manager container running on a vps with custom ports and it's working. It's not the latest version tho
  5. ok, we are in the same boat sir 😂 Let's see if someone more experienced can work it out somehow. Anyway, this container is the most usefull i am running right now. I can't believe the simplicity of this tool
  6. did you configure Nextcloud to work with https ?
  7. Hello! Yuo helped me a lot with your videos and after all your tutorials i followed i pulled the trigger on an intel 4 1gb ports nic. The problem is that i realized too late my 2500k doesn't support vt-d, so i can't passthrough the PCI-e card to the VM. Are there any ways i can install pfSense on a VM? The hardware configuration is like this: ISP Modem/Router -> Switch -> unRaid Machine at eth port on motherboard. I am not a pro in networking and i can't figure out how to configure the 4 ports nic.
  8. Hi guys! I really need some help, because i am new to reverse proxy/letsencrypt thing. Basically, i followed Spaceinvader One video about Nextcloud and letsencrypt: No problems for nextcloud, but i can't configure gitea. I created the file: user/appdata/letsencrypt/nginx/proxy-confs/gitea.subdomain.conf server { listen 443 ssl; server_name gitea.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_gitea gitea; proxy_pass https://$upstream_gitea:3000; } } Then edited the gitea config file: [server] APP_DATA_PATH = /data/gitea SSH_DOMAIN = gitea.mypersonaldomain.com HTTP_PORT = 8300 ROOT_URL = https://gitea.mypersonaldomain.com:8300 DISABLE_SSH = false SSH_PORT = 8022 LFS_CONTENT_PATH = /data/git/lfs DOMAIN = gitea.mypersonaldomain.com LFS_START_SERVER = true LFS_JWT_SECRET = *********************************** OFFLINE_MODE = false The container uses port 8300 and 8022 for ssh. The best i get is a 502 error when visiting gitea.mypersonaldomain.com:8300. With these settings, the gitea web interface is unreachable even if i point to my localhost ip ( 192.168.1.200:8300 ) Any tips ?