As I want to share some of my directories to my Windows PCs in the LAN, I would like to activate the samba server via OSMC settings - shopping cart.
But when clicking the cart symbol nothing happens.
I’ve installed RC3 a month ago and today I did a
sudo apt-get dist-upgrade
via a ssh console which seemd to succeed.
A little bit strange: A former update via the GUI failed; same with apt-get update at the console. At the GUI there is still a 0.9.9 release number.
Access to Debian sources seems to be ok but there is a problem access to apt.osmc.tv like this:
Err http://apt.osmc.tv jessie/main armhf Packages
404 Not Found
Ign http://apt.osmc.tv jessie/main Translation-en
Fetched 734 B in 16s (44 B/s)
W: Failed to fetch http://apt.osmc.tv/dists/jessie/main/binary-armhf/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
osmc@osmc:/etc/samba$
Can you get to the link that failed in your PC’s browser ?
Are you on a home network or business ? Do you have an unusual proxy server or hardware firewall ?
Has updating ever worked before ? You say you did ‘sudo apt-get dist-upgrade’ but did you remember to do ‘sudo apt-get update’ first ?
Or for that matter, have you tried the built in updater in MyOSMC ?
Ok. Thanks for looking into this. I’ll try to sort that out:
- Yes. I can get the link in my PCs browser, which is located in the same LAN. It shows a ftp-like page starting with “Index of /osmc/apt”
- I’m in my home network. There is no special firewall, only a standard home router device.
- At first I tried the built in updater in MyOSMC. It always ended up in a dialog box showing an error and asking to post it here in the forum (I saw the same right after my first install a month ago)
- After that I changed over to the ssh-console, starting with sudo apt-get update → some errors. But some of the downloads (the ones which come from ubuntu) seem to succeed.
- After that I did the dist-upgrade which finished without errors. But as a matter of fact I still see the version number RC3 0.9.9 in MyOSMC.
- Again I tried now to update via MyOSMC: First I see a dialogue with the error message; after clicking it away a couple of seconds later a second one comes up reporting everything is fine ?! (but still RC 0.9.9 …)
My Logfiles are here: http://paste.osmc.io/casiyagigi
Since I’ve also a working owncloud installation up on this device I would appreciate it to get some help to fix this problem than to start over with a fresh install.
Thanks in advance.
Volker
Have you tried changing the DNS on the OSMC system to 8.8.8.8 (google public DNS)?
Not yet. DNS server is my home router (supplied via DHCP as for all my other devices in the Home-LAN). As I don’t have any resolving problems from these devices…
Moreover (from the console of my RPI2 under OSMC):
ping apt.osmc.tv
replies immediately with
PING apt.osmc.tv (46.37.172.210): 56 data bytes
64 bytes from 46.37.172.210: seq=0 ttl=47 time=36.441 ms
…
Hmmm. Interesting. By typing apt.osmc.tv in the browser I get back
http://46.37.189.135/osmc/apt/
which is a different address.
Wireshark tells me, that 46.37.172.210 answers via http with a new address 46.37.189.135 to follow, where the browser finally gets the correct ftp-like page.
Changing my DNS on the OSMC system does’t change anything…
In my apt/sources.list:
…
deb http://apt.osmc.tv jessie main
By starting the update I get:
osmc@osmc:/etc$ sudo apt-get update
Hit h…://ftp.debian.org jessie InRelease
Hit h…://ftp.debian.org jessie-updates InRelease
Hit h…://security.debian.org jessie/updates InRelease
Ign h…://apt.osmc.tv jessie InRelease
Ign h…://apt.osmc.tv jessie Release.gpg
Ign h…://apt.osmc.tv jessie Release
Err h…://apt.osmc.tv jessie/main armhf Packages
Strange:
osmc@osmc:~$ wget http://apt.osmc.tv/dists/jessie/InRelease
converted ‘http://apt.osmc.tv/dists/jessie/InRelease’ (ANSI_X3.4-1968) → ‘http://apt.osmc.tv/dists/jessie/InRelease’ (UTF-8)
–2015-07-14 22:05:10-- http://apt.osmc.tv/dists/jessie/InRelease
Resolving apt.osmc.tv (apt.osmc.tv)… 46.37.172.210
Connecting to apt.osmc.tv (apt.osmc.tv)|46.37.172.210|:80… connected.
HTTP request sent, awaiting response… 302 Found
Location: http://46.37.189.135/osmc/apt/dists/jessie/InRelease [following]
converted ‘http://46.37.189.135/osmc/apt/dists/jessie/InRelease’ (ANSI_X3.4-1968) → ‘http://46.37.189.135/osmc/apt/dists/jessie/InRelease’ (UTF-8)
–2015-07-14 22:05:10-- http://46.37.189.135/osmc/apt/dists/jessie/InRelease
Connecting to 46.37.189.135:80… connected.
HTTP request sent, awaiting response… 404 Not Found
2015-07-14 22:05:11 ERROR 404: Not Found.
Here is the result of a tcpdump from my osmc machine:
GET /osmc/apt/dists/jessie/InRelease HTTP/1.1
User-Agent: Wget/1.16 (linux-gnueabihf)
Accept: /
Host: 46.37.189.135
Connection: Keep-Alive
HTTP/1.1 404 Not Found
Pragma: no-cache
Connection: close
Content-type: text/html; charset=utf-8
Content-Length: 4035
The same http works perfect in my browser on the Windows-PC:
GET /osmc/apt/dists/jessie/InRelease HTTP/1.1
Host: 46.37.189.135
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
Accept-Language: de,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate
Connection: keep-alive
HTTP/1.1 200 OK
Date: Tue, 14 Jul 2015 20:12:01 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Mon, 06 Jul 2015 22:11:51 GMT
ETag: “e64-51a3c314c57c0”
Accept-Ranges: bytes
Content-Length: 3684
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Very unusual. It’s going to be something specific to your internet connection though as there are a few hundred thousand OSMC users and no other reports of this problem.
My best guess is that your ISP is passing you through a transparent proxy (many/most ISP’s do) but that proxy is not liking the user agent that OSMC is using…Notice that on the HTTP 404 response there is no Server: field - this 404 response is probably coming from your ISP’s transparent proxy.
Can you try the following two commands from OSMC and log the traffic again with wireshark ?
wget --server-response --spider http://46.37.189.135/osmc/apt/dists/jessie/InRelease
wget --server-response --spider --user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0" http://46.37.189.135/osmc/apt/dists/jessie/InRelease
The second one changes the user agent to the same user agent as your PC browser…
When I run this test I get the same results with both versions of the command.
And here we go:
I turned on the blacklist rule on my internet router for this device to prevent my kids from visiting bad sites. And it seems as if the osmc site is on the blacklist. 
Turning it off gives free access for updates. That processed now without errors.
Thanks a lot for your help.
Well that explains that then…