littlebudha

Members
  • Posts

    26
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

littlebudha's Achievements

Newbie

Newbie (1/14)

4

Reputation

  1. Did you follow the instructions from Spaceinvaders youtube video to make sure you have the initial setup working ( ) once you get this working, follow above instructions.
  2. So those of you who live in an area where locast is not available you can follow these instructions to route your locast traffic through a Docker container with VPN built in already: - I used the excellent instructions by @Cynagen to get my locast2Plex setup - I then used the instructions provided by @SpaceInvaderOne to route traffic through a container already having VPN built in. i used the binhex-delugevpn, but you can use any container you want. Instructions for this are available as a video on : https://www.youtube.com/watch?v=5AEzm5y2EvM and https://www.youtube.com/watch?v=znSu_FuKFW0&t=457s - once the VPN container is created and working, make sure the traffic is going through the VPN, Make sure the VPN server is located in the market that locast is available. I used PIA and Atlanta as the server. then add following ports to this container: Name: locast2plex , Host Port: 6077, connection type : TCP Name: Locast2Plex service Port: Host Port: 1900, connection type: TCP - Start this VPN container - then follow the instructions provide above by @Cynagen with the following modifications: in the locast2plex container, make sure and choose Advanced configuration under extra parameters add: --net=container:binhex-delugevpn ( or any name of the VPN container you chose) Network must be NONE External Address is the address of the VPN containers IP address ( In mycase its the delugeVPN container address) I had to keep Priviladged OFF, but not sure if required rest of the settings are same @Cynagen start the container and under the log it should start up normally if everything is correct. You do need to donate to locast to make this work in plex Live TV and DVR you would add the IP address of your VPN container with port 6077 choose the zipcode of the market you chose for me it was atlanta, and the EPG has an option for Locast OTA data. ENJOY!
  3. Thank you very much for this! I got my Locast2Plex to work with these instructions!
  4. Can someone create a Template for tgorg's locast2plex docker? Also, if its possible to add built in open VPN support inside it so we can change the location of the ipAddress. I really would appreciate this! trying to set it up through dockerhub, but I think lots of people will find this container VERY useful!
  5. Im sorry if Im asking basic questions, but whats the difference between the xteve containers? Also, does the VPN container route all streaming data from the IPTV through a VPN or does it only route the guide DATA? thanks!
  6. So I have cloudflare and Nginx proxy manager working. make sure all the port forwarding is setup per your router to the Nginx container I went onto cloudflare and created my cnames for my domain under DNS Then went to crypto tab and created the origin certificates - you can create individual one for each subdomain or have one with all the subdomain added. this will give you the .PEM and .Key you save these on to your desktop as whateveryouwanttocallit.pem and whateveryouwanttocallit.key goto ngnx proxy manager and goto SSL certificates create a custom certificate only need the .pem and .key files to create a new certificate once this creates it ogot the Hosts > Proxy Host tab create your proxy host Fill out the details Tab --> then under SSL tab choose the custom certificate This setup works for me. I cannot use force SSL tab, if I do so then I get errors for some reason I also setup the firewall rules on cloudflare to block all non US web requests.
  7. Have you created the origin certificate in cloudflare (under Crypto Tab)? once you create these you save them as .pem and .key files. Use these to create the SSL certificate in proxy manager. I had to use these SSL certificate to make it work instead of the letsencrypt ones.
  8. SO I tried this and it worked. The lidarr server is loading now, but I get this error 2018-03-17 11:59:39,706 DEBG 'lidarr' stdout output:[Info] RefreshArtistService: Updating Info for YFN Lucci2018-03-17 11:59:40,305 DEBG 'lidarr' stdout output:[Error] RefreshArtistService: Couldn't refresh info for [93cc3f11-751a-48d4-aaaf-ebad6cd0526d][YFN Lucci][v0.2.0.301] NzbDrone.Common.Http.HttpException: HTTP request failed: [500:InternalServerError] [GET] at [https://api.lidarr.audio/api/v0.3/artist/93cc3f11-751a-48d4-aaaf-ebad6cd0526d?primTypes=Album&secTypes=Studio]at NzbDrone.Core.MetadataSource.SkyHook.SkyHookProxy.GetArtistInfo (System.String foreignArtistId, System.Int32 metadataProfileId) [0x001af] in C:\projects\lidarr\src\NzbDrone.Core\MetadataSource\SkyHook\SkyHookProxy.cs:92at NzbDrone.Core.Music.RefreshArtistService.RefreshArtistInfo (NzbDrone.Core.Music.Artist artist) [0x0001f] in C:\projects\lidarr\src\NzbDrone.Core\Music\RefreshArtistService.cs:63at NzbDrone.Core.Music.RefreshArtistService.Execute (NzbDrone.Core.Music.Commands.RefreshArtistCommand message) [0x000aa] in C:\projects\lidarr\src\NzbDrone.Core\Music\RefreshArtistService.cs:172{"error": "Error -2 connecting to redis:6379. Name or service not known."} and it does not get me to start screen of lidarr app.
  9. SO I am currently using Unraid 6.4.1. I am using Ubiquiti as my networking gear including USG for router and Unifi Switches. I am using multiple dockers currently for Plex, Sonarr, SabzNzbd, Deluge, etc. The way I have it set is: when I create a docker I am assigning them a static IP in the same range as assigned by my DNS server on USG: set yo 192.168.1.1/24. so I would set network type to eth0. Fixed IP address of : for deluge 192.168.1.210 and for plex 192.168.1.211, etc on my USG, it shows up as the corresponding IP address and I assign a static IP address and name it: Plex server, Deluge server. This seems to work well for me. My question is: Am I doing it wrong? is there any disadvantage to doing it this way? Is there a better way? Thanks in advance
  10. Hey dlmh, Thanks for the input... I also noted that there is a AFP and netatalk posts and edits. I was wondering if there are any advantages to installing the AFP and netatalk? Are they working well? I'm able to see the unraid server on time machine right now, but it shows it as a one large share and not individual use shares... anyways didn't mean to change the thread topic thanks
  11. Here is the samba.service file... <port>139</port> <host-name>Tower.local</host-name> in this spot I tried changing the host name to 10.0.1.4 or media and changed the port as well samba.service.txt
  12. here is the syslog ... thanks for looking into it... syslog-2010-03-25.txt
  13. Hey ALL! Thanks for working on this so that us mac users can have a easy way connecting to our unraid box. I have followed the instructions as stated and at the end of it I can see in my finder the uraid box ( i think). It shows up when I drop in the .service file in the services folder. So I'm assuming it seems to announce the server. The problem is I can't connect to the server. At the end of trying to connect it states the connection failed. When I click on connect as... it wont show the username password dialogue. I do connect to my server using an IP address: 10.0.1.4 and I tried using that as the name of the server where we use tower.local but still could not connect. I tried changing the ports, and still no go. Is there anything I'm missing? I'm not getting any errors when I install all 4 packages, or when I start the Daemon or restart avahi. Any help would be appreciated. Thanks