4.7 "Server is not accessible or remote file is not present on it" mystery problem
Posted: 26 Jul 2018, 23:58
The following can't be a bug, can it?
I've successfully used PK Cloud versions from 4.4 to 4.6, with the same setup procedure I successfully read the remote kiosk config files and devices connect and, if necessary, update, burn and reboot, all quickly and reliably.
I am now mystified why 4.7 Cloud version will verify the remote kiosk config file upon setup but when the device has rebooted I get the error message
Server is not accessible or remote file is not present on it
If I then type in the location of the config file into the browser it immediately displays correctly.
I am not using Porteus server, the config file for 4.7 is located in exactly the same location as all the other PK version config files.
I have compared a 4.6 to a 4.7 config file, line by line using Notepad++, and they are formatted correctly and indentically, apart from the reference to the config file [4.6 points to xyzkiosk46.txt and 4.7 points to xyzkiosk47.txt]
I have downloaded the 4.7 kiosk iso cloud version multiple times, in case there was a corruption.
I have read the troubleshooting section here http://porteus-kiosk.org/server.html#troubleshooting and am, again, working my way through the remote management steps.
I will now try to read the 4.7 config file from a different location also.
edit: didn't make any difference. I still see the same error message.
edit 2: just did the entire process on the same device with pk 4.6 cloud edition, pointing to a xyzkiosk46.txt and the process was perfectly successful.
I also tried the pk cloud edition 4.7 setup, pointing it to xyzkiosk46.txt config file [just in case it was a problem with the xyzkiosk47.txt config file] and got the error message 'Server is not accessible or remote file is not present on it".
Is there something changed/updated on comms modules on 4.7 that doesn't give the OS enough time to discover and read the config file on boot up?
I must have obviously missed something simple but I am at a loss what I am doing wrong.
And, just on the off chance, is the initially generated kiosk config file written with the parameters in the same order as 4.6? Would that even make any difference?
I would be grateful for a 'sanity check' from wiser and experienced forum users.
In the meantime I'll be running the debug option on my 4.7 config file.
edit: done and sent logfile to the very kind people at Porteus.
I've successfully used PK Cloud versions from 4.4 to 4.6, with the same setup procedure I successfully read the remote kiosk config files and devices connect and, if necessary, update, burn and reboot, all quickly and reliably.
I am now mystified why 4.7 Cloud version will verify the remote kiosk config file upon setup but when the device has rebooted I get the error message
Server is not accessible or remote file is not present on it
If I then type in the location of the config file into the browser it immediately displays correctly.
I am not using Porteus server, the config file for 4.7 is located in exactly the same location as all the other PK version config files.
I have compared a 4.6 to a 4.7 config file, line by line using Notepad++, and they are formatted correctly and indentically, apart from the reference to the config file [4.6 points to xyzkiosk46.txt and 4.7 points to xyzkiosk47.txt]
I have downloaded the 4.7 kiosk iso cloud version multiple times, in case there was a corruption.
I have read the troubleshooting section here http://porteus-kiosk.org/server.html#troubleshooting and am, again, working my way through the remote management steps.
I will now try to read the 4.7 config file from a different location also.
edit: didn't make any difference. I still see the same error message.
edit 2: just did the entire process on the same device with pk 4.6 cloud edition, pointing to a xyzkiosk46.txt and the process was perfectly successful.
I also tried the pk cloud edition 4.7 setup, pointing it to xyzkiosk46.txt config file [just in case it was a problem with the xyzkiosk47.txt config file] and got the error message 'Server is not accessible or remote file is not present on it".
Is there something changed/updated on comms modules on 4.7 that doesn't give the OS enough time to discover and read the config file on boot up?
I must have obviously missed something simple but I am at a loss what I am doing wrong.
And, just on the off chance, is the initially generated kiosk config file written with the parameters in the same order as 4.6? Would that even make any difference?
I would be grateful for a 'sanity check' from wiser and experienced forum users.
In the meantime I'll be running the debug option on my 4.7 config file.
edit: done and sent logfile to the very kind people at Porteus.