Hello,
Following the directions on Creating a Local AREDN® Software Server, I set one up on a Linux machine connected to of our nodes a week ago, and wrote a script for my team and I to keep them updated in each region. However, I quickly noticed that even though nightly builds were being provided, the software server was not showing them. Eventually, I discovered that the afs/misc/collect.py script that updates the JSON targets was also removing the new versions from afs/www/config.js that were just synced over. As a result, we are permanently stuck with offering whichever versions you originally downloaded on day one. You can, however, manually navigate the tree to download the file you want, but I am certain the python script was not intended to make changes to the config.js. As a work around, I make a backup copy of the config.js before running the python script and restore it after the script completes. This has fixed (or band-aid) the issue for now. Deleting the entire root directory and starting fresh also works,
.
However, now, I am getting SSL errors. Even though the URL to the nodes is http:// (which should had been pushed out to the JSON targets), the kernel and sysupgrade buttons are https://. Clicking them gives an ERR_SSL_UNRECOGNIZED_NAME_ALERT I do not know if those links were always https://, I just know that I could manually download any AREDN software previously, and now I get the SSL error. I am still troubleshooting this issue, as I only discovered this today. Rewrites have not worked (yet). I am using NPM and Fileserver to run the server on and have tested Edge, Firefox, Vivaldi, Brave, and Safari browsers.
Thanks for you help!
Tony
Following the directions on Creating a Local AREDN® Software Server, I set one up on a Linux machine connected to of our nodes a week ago, and wrote a script for my team and I to keep them updated in each region. However, I quickly noticed that even though nightly builds were being provided, the software server was not showing them. Eventually, I discovered that the afs/misc/collect.py script that updates the JSON targets was also removing the new versions from afs/www/config.js that were just synced over. As a result, we are permanently stuck with offering whichever versions you originally downloaded on day one. You can, however, manually navigate the tree to download the file you want, but I am certain the python script was not intended to make changes to the config.js. As a work around, I make a backup copy of the config.js before running the python script and restore it after the script completes. This has fixed (or band-aid) the issue for now. Deleting the entire root directory and starting fresh also works,
.However, now, I am getting SSL errors. Even though the URL to the nodes is http:// (which should had been pushed out to the JSON targets), the kernel and sysupgrade buttons are https://. Clicking them gives an ERR_SSL_UNRECOGNIZED_NAME_ALERT I do not know if those links were always https://, I just know that I could manually download any AREDN software previously, and now I get the SSL error. I am still troubleshooting this issue, as I only discovered this today. Rewrites have not worked (yet). I am using NPM and Fileserver to run the server on and have tested Edge, Firefox, Vivaldi, Brave, and Safari browsers.
Thanks for you help!
Tony