• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. dcorpening
    3. Topics
    D
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 13
    • Groups 0

    Topics

    • D

      Upgrading from 1.2.0 to 1.3.0 failed.

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems upgrade 1.2.0 1 1.3.0 trunk
      2
      0 Votes
      2 Posts
      750 Views
      Wayne WorkmanW

      I’ve seen something like this before in the forums, it was related to a proxy server and ssl.

      Does your web connection go through a proxy? Do you have a caching server like squid?

      Here’s related issues, they all seem to have the same answer:
      http://askubuntu.com/questions/186847/error-gnutls-handshake-failed-when-connecting-to-https-servers
      http://unix.stackexchange.com/questions/302839/gnutls-handshake-failed
      http://devopscube.com/gnutls-handshake-failed-aws-codecommit/

    • D

      Transferring all images & all host info from (1.2.0) to (1.2.0)

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems migrate upgrade move
      27
      0 Votes
      27 Posts
      7k Views
      Wayne WorkmanW

      @Tom-Elliott said in Transferring all images & all host info from (1.2.0) to (1.2.0):

      The older export system (1.2.0 and earlier back to 1.0.0 when it was introduced) didn’t take into account the tables existing.

      @Moderators important tid-bit of info there.

    • 1 / 1