I understood that the url was obfuscated.
Nevertheless, the 403 code means that the server forbids your client.
Do you use a VPN on your RPis and not on your other systems?
I understood that the url was obfuscated.
Nevertheless, the 403 code means that the server forbids your client.
Do you use a VPN on your RPis and not on your other systems?
Display MoreSame problem...
2020-10-15 22:10:52.190 T:1807721344 ERROR: CCurlFile::FillBuffer - Failed: HTTP returned error 403
2020-10-15 22:10:52.190 T:1807721344 ERROR: CCurlFile::Open failed with code 403 for http://aaaaa.com/bbb:
2020-10-15 22:10:52.190 T:1807721344 ERROR: Open - failed to open source <http://aaaaa.com/bbb>
2020-10-15 22:10:52.190 T:1807721344 ERROR: AddOnLog: PVR IPTV Simple Client: Unable to load playlist file http://aaaaa.com/bbb': file is missing or empty.
It suddenly stoped working...
The same URL works fine on GSE IPTV on iPhone/Android, the channels URLs works normally on VLC...
Only LibreElec / IPTV Simple Client stoped working
Running on RPI3 + LibreElec 9.2.4 and also in a RPI1 + LibreElec 9.2.4. Both stoped working.
Even the weather ADDON stoped working - even with all internet connection tests working fine.
Is there any update on LibreElec that could cause general curl/connectivity problems?
So weird...
Guilherme
The HTTP 403 Is a HTTP status code meaning access to the requested resource is forbidden for some reason. The server understood the request, but will not fulfill it due to client-related issues.
Check http://aaaaa.com/bbb with a browser. This might provide information about your issue.
The server might not like the user-agent used by IPTV simple.
It looks like your device is not connected to the network. Check the network connection. Also, if the network connection is slow to set up (wifi), enable the wait for network setting in the LibreELEC network settings.
I tried creating that, and it didn't work. And I tried the normmal manual ways of mounting a samba share, and that didn't work either. So what I WAS wondering about was, in what way is this distro different, since the standard linux smb commands claims that the share and server doesn't exist.
You say you tried to create a system.d configuration file, but you neither provide that file, nor the reason (error message) why it fails.
You say you tried the normal way, but you neither describe the normal way nor how it fails.
Someone might help you if you provide more details about what you are trying to do and how it fails.
No. I'm trying to mount a Samba share on the LibreElec. The Samba share is hosted on an Linux OSMC server on another raspberry pi, which is pretty similar to LibreElec.
What is your system.d configuration file?
Ok can you help me out please, what should I run in a RPI4 to used VNC
The Raspberry Pi VNC addon.
You can find it in the LibreELEC addons.
On Raspberry Pi use the Raspberry Pi VNC addon from the LibreELEC addons
If you really can't route, then configure tinc in switch mode and set both the network and tinc devices of LibreELEC in promisc mode. You might even not need routes (just 192.168.1.20x/32) if the arp tables are propagated.
Unless you bridge your devices, the tinc subnet should be different from the lan subnet. It can be a subnet of the lan subnet or a different subnet. Traffic must somehow be routed: you can add a route in your dhcp server for that.
I do not understand your configuration. Why do you use two subnets?
It has been a long time that I have not played with tinc, but I remember that it was complicated.
Some advice:
- on LibreELEC, use an interface name that is blacklisted by connman, eg vmnet_foo, to prevent connman from messing with its configuration,
- by default interfaces on LibreELEC will not forward traffic, so you have to enable ip forwarding (for tinc in router mode) or promiscuitous mode (for tinc in switch mode),
- use two addresses of your home network for the tinc interfaces (home ip 192.168.1.200 with a route to remote 192.168.0.201, remote ip 192.168.1.201 with a route to 192.168.1.0/24 via 192.168.0.200)
- I vaguely remember static routes on the router and/or brutils.
It will therefore probably be easier to configure a device more suitable to your purpose than a LibreELEC mediacenter
Hi,
Syncthing is not running anymore on LibreELEC 9.2.2. I've installed latest "Syncthing for Kodi addon 9.2.0.109" that seems to use syncthing 1.4.2. but current syncthing binary version is 1.9.0. Can you provide an update for Kodi please?
Code Display More$ journalctl -u service.system.syncthing Sep 15 20:52:36 kronos systemd[1]: Starting Syncthing - Open Source Continuous File Synchronization... Sep 15 20:52:36 kronos systemd[1]: Started Syncthing - Open Source Continuous File Synchronization. Sep 15 20:52:36 kronos sh[1854]: [start] INFO: syncthing v1.4.2 "Fermium Flea" (go1.12.6 linux-amd64) unknown@unknown 1970-01-01 00:00:00 UTC Sep 15 20:52:36 kronos sh[1854]: [start] WARNING: Failed to initialize config: config file version (31) is newer than supported version (30). If this is expected, use -allow-newer-config to override. Sep 15 20:52:36 kronos systemd[1]: service.system.syncthing.service: Main process exited, code=exited, status=1/FAILURE Sep 15 20:52:36 kronos systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'. Sep 15 20:52:36 kronos systemd[1]: service.system.syncthing.service: Service RestartSec=100ms expired, scheduling restart. Sep 15 20:52:36 kronos systemd[1]: service.system.syncthing.service: Scheduled restart job, restart counter is at 1. Sep 15 20:52:36 kronos systemd[1]: Stopped Syncthing - Open Source Continuous File Synchronization.
This repeats 5 times until it fails...
Code Display MoreSep 15 20:52:37 kronos systemd[1]: Starting Syncthing - Open Source Continuous File Synchronization... Sep 15 20:52:37 kronos systemd[1]: Started Syncthing - Open Source Continuous File Synchronization. Sep 15 20:52:37 kronos sh[1958]: [start] INFO: syncthing v1.4.2 "Fermium Flea" (go1.12.6 linux-amd64) unknown@unknown 1970-01-01 00:00:00 UTC Sep 15 20:52:37 kronos sh[1958]: [start] WARNING: Failed to initialize config: config file version (31) is newer than supported version (30). If this is expected, use -allow-newer-config to override. Sep 15 20:52:37 kronos systemd[1]: service.system.syncthing.service: Main process exited, code=exited, status=1/FAILURE Sep 15 20:52:37 kronos systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'. Sep 15 20:52:37 kronos systemd[1]: service.system.syncthing.service: Service RestartSec=100ms expired, scheduling restart. Sep 15 20:52:37 kronos systemd[1]: service.system.syncthing.service: Scheduled restart job, restart counter is at 5. Sep 15 20:52:37 kronos systemd[1]: Stopped Syncthing - Open Source Continuous File Synchronization. Sep 15 20:52:37 kronos systemd[1]: service.system.syncthing.service: Start request repeated too quickly. Sep 15 20:52:37 kronos systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'. Sep 15 20:52:37 kronos systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization.
Thanks!
You could try to do the following in the console.
1. Create a dummy directory:
mkdir -p /storage/downloads/dummy
2. Run a dummy syncthing service:
STNODEFAULTFOLDER="y" syncthing -home=/storage/downloads/dummy -gui-address"0.0.0.0:23456"
3. Browse to http://libreelec.local:23456 and update syncthing to the latest version.
4. Stop the dummy syncthing with ctrl-c.
5. Restart syncthing:
systemctl restart service.syncthing
I would really like to get tinc working as I have to use specific port to connect (work place firewall)
Wireguard is using udp only as zerotier is Trying my best with openvpn-as from linuxserver but tinc looks like its much more efficient for me
Then use the --config flag of the tinc/tincd commands to store your custom configuration in a separate directory, and follow the tinc documentation. It should not be too hard
To clarify, you can use the tinc binary provided by the addon to use all tinc features, but you will have to configure it yourself because the addon is only designed for point-to-point connections.
Zerotier One without Docker was mentioned here and there in this forum.
Wireguard is indeed also an option.
As far as I know, routing is disabled by default on LibreELEC, but you can enable it by setting /proc/sys/net/ipv4/ip_forward to 1.
Hi awiouy. Sorry to dig so old thread but I'm having hard time here for last couple of hours trying to set your addon together with android tinc app.
So my question is did you compile this addon with router mode as its the only mode tinc android support?
Will this vpn let me connect from my phone outise of my house to network with my home ip address?
The addon uses router mode but LibreELEC will not route external trafic towards its local network.
Also, the addon uses tinc 1.1, which is not compatible with tinc 1.0.
In other words, the addon is useful to connect two (LibreELEC) devices point-to-point.
You can nevertheless use the tinc binary provided by the addon (as opposed to the service of the addon) to achieve whatever you need.
But nowadays there are more straightforward solutions, such as zerotier-one.
You could also have a look at the transcoding settings of Emby.