@sebastian-roth I’ll try to make it clearer - on install if I select HTTPS it will not install because of the certificate error.
If you install without selecting HTTPS - it installs and works beautifully, when it checks for the token it automatically updates the settings.json file to support HTTPS without any action.
So yes it is currently working.
@sebastian-roth The client works great if I don’t install with HTTPS, I get the same error if I use HTTPS on install.
The cool thing though - if I install without https, it looks for the token, can’t find it and automatically switches to HTTPS in settings on it’s own.
So if I uncheck the box for HTTPS while installing the client it will go in. If I try to repair I get the unable to install CA certificate. If I try to install with HTTPS checked, I get the same thing.
I went to the address for my server, downloaded the cert from where it says not secure and added it to my trust root certificates - no change.
In my log it shows a communication error - tried to download the cert, and it says could not download file. I put the address in the browser and download manually and install the cert, again nothing changes.
After installing the 2 certs from the fog folder and the srvpublic cert I started getting another error. “Unable to get subsection” then the next line “Object reference not set to an instance of an object”
I’m able to capture an image, deploy an image - but I can’t get the client to work.
@sebastian-roth
I was able to figure it out - when I made the vm that I took my image from my fog-server address was different as I installed it many times trying to get it to work.
The machine I captured the image from had the fog-client pointed to the old server, once I removed the fog-client and reinstalled with the FQDN it did the trick.
Thank you
once I reimaged again - it’s again trying to pull the certificate from 186, I wonder if that’s due to the image itself?
Maybe I built the client I pulled the image from and it had my old server name in it? Only thing I can think of, although I’m not sure how
we recreated the certificate through the server it now shows the correct ip address inside the certificate, going to reimage the client and see if it takes
After deploying an image - I attempted to push out a snap in which I built and it kept failing authentication saying certificate is not from Fog CA.
My fog server is at 10.0.0.165 but the ip in the certifcate is 10.0.0.186 - that was also in the json file which I modified to show as 165.
Why on earth would it show a different ip like that? I checked my DNS records, those are set correctly, same with my DHCP. If I ping fog-server.domain it comes back with 165.
Not sure where this would get messy but any help would be appreciated.
I was trying to capture an image, it continued - later popped an error that the drive was unclean on 2 different laptops, to perform a full shutdown. I am capturing currently from a VM.
Fog version 1.5.9
Not sure sure on kernal version, running the newest version of Ubuntu currently - may switch to full debian.
ACPI Error: Field (CAP1) at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20180810/dsopcode-201)
ACPI Error: Method parse/execution failed _SB._OSC, AE_AML_BUFFER_LIMIT (20180810/psparse-516)
I typed that by hand so hopefully I didn’t make any errors - but does anyone have any idea what this is or how to fix?