Skip to main content
Question

Issues with new Reposado configuration

  • July 20, 2018
  • 6 replies
  • 15 views
easyedc
Forum|alt.badge.img+16

So I've started testing out replacements for my old ASUS and am seeing if Reposado can do what I need it to. Currently running on macOS Server. Any attempt to connect and check for updates gives some vague (to me) errors. I've tried to set the URL of the SUS to be both the IP and the hostname.local of the server. No luck with those, just similar errors. 

macOS Test Box:~ root# softwareupdate --set-catalog http://123.456.789.123/content/catalogs/others/index-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
Changed catalog to http://123.456.789.123/content/catalogs/others/index-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
macOS Test Box:~ root# softwareupdate -la
Software Update Tool

Finding available software
Can’t connect to the Software Update server (123.456.789.123).

macOS Test Box:~ root# softwareupdate --set-catalog https://123.456.789.123/content/catalogs/others/index-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
Changed catalog to https://123.456.789.123/content/catalogs/others/index-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
macOS Test Box:~ root# softwareupdate -la
Software Update Tool

Finding available software
An SSL error has occurred and a secure connection to the server cannot be made.
macOS Test Box:~ root#

I am sure it's in my macOS server's website configuration that's causing this, but I'm at a loss for troubleshooting.

  • I've checked that I have an SSL cert (self-signed)
  • I've tried browsing to the update url in the server's browser and other Macs with no luck
  • I can ping the computer hosting the server
  • can browse other sites from the server
  • Reposado does appear to be doing its thing, since all the updates have been copied down.

At this point I'm sort of stumped. And if you couldn't tell, this IS my first time at this particular rodeo.

    6 replies

    N
    Forum|alt.badge.img+13
    • Nix4Life
    • Honored Contributor
    • July 20, 2018

    @easyedc

    not sure which guide you used to setup your server, but double check your settings here against Alan Siu's. It could be permissions on the html directory. "I've tried browsing to the update url in the server's browser and other Macs with no luck". if you can't browse, then it's not working. Once you get it working you should look into mod rewrites so you can use one designation for your clients, ie https://123.456.789.123/index_prod.sucatalog

    reposado docs
    slack #reposado

    J
    Forum|alt.badge.img+3
    • jm_peterson
    • New Contributor
    • July 20, 2018

    @easyedc The App store will not let you pull updates from a server using a self-signed SSL cert in my experience. I recently set up a Reposado server on Centos 7 and initially used a self-signed cert and got the same error. If you open the App Store and go to the Updates tab it will prompt you saying the server is not trusted.
    Once I added my RapidSSL cert everything started working.

    U
    Forum|alt.badge.img+6

    Do you have any proxy in place ? And have you updated Proxy profile in preferences.plist in reposado?

    Not sure if this is really blocking you. Just an Idea to check from that level as well.

    easyedc
    Forum|alt.badge.img+16
    • easyedc
    • Author
    • Esteemed Contributor
    • July 23, 2018

    So I solved part of my problem. When I was setting up my website I didn't point to the right directory (was pointing to /Volumes/Reposado/reposado instead of needing to point to /Volumes/Reposado/reposado/html) and so now browsing to my url works and shows an .xml of all the available updates. Now I'm running into an issue of not actually seeing any updates. From a test box running 10.13.3:

    macOS Test Box:~ root# softwareupdate --set-catalog http://123.456.789.123/content/catalogs/others/index-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
Changed catalog to http://123.456.789.123/content/catalogs/others/index-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
macOS Test Box:~ root# softwareupdate -la
Software Update Tool

Finding available software
No new software available.
macOS Test Box:~ root#
    easyedc
    Forum|alt.badge.img+16
    • easyedc
    • Author
    • Esteemed Contributor
    • July 23, 2018

    ...And I think I have this solved. I'd created a few websites in frustration trying to get this to all work. I also created several certs, too. By making sure that my active site was using the correct certificate, it's now working as expected. Now to test.

    S
    Forum|alt.badge.img
    • SMR
    • New Contributor
    • November 13, 2019

    I know this is an old thread, but there aren't many out there.This is my first time trying to set this up. I'm following Alan Siu's site and attempting to set this up on a Mac Mini. I created the html and metadata folders and did the sync. I think my issue is with the getting the base URL setup. I'm not exactly sure what to put. I tried using https://servername.domain.com and even the IP address followed by /content/catalogs/others/index-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1_testing.sucatalog. I did create a test index file under the documents file and if I go to another Mac and type in http://sdmdeploystudio it shows the content of the html file.

    Terms & ConditionsCookie settingsAccessibility statement