From: Oboe Lova <cfytech24x7@gmail.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Qualified success with 8.0-2
Date: Mon, 30 Oct 2023 14:46:13 -0600 [thread overview]
Message-ID: <CAC04G9h0iv6+tQ3-=StjZKT+xOaTZY=_zqZf8ELRDx-=JVi9kQ@mail.gmail.com> (raw)
Your screen images allowed me to finally see how I do a manual upload of
any VM candidate image to the pve storage BEFORE trying to pick it as the
VM image in the web gui. I was able to install bookworm as a vm and use
it to browse the internet via a QEMU console on the pve host.
But perversely, neither Chrome nor Firefox, which worked normally earlier
this morning now allow me to use the url to start the web gui to the pve.
I tried other browsers and they treat https://n.n.n.n:8006/ as a document
name. I also noticed that google pushed on update to my Chrome brower on
my laptop.
So now big tech is invading my home to disable my tinkering with computers
on a an RFC private network?
Google has put a small notice at the bottom of my browse window and here is
a quote from it
"More about SafeSearch
SafeSearch is designed to detect explicit content like pornography and
graphic violence on Google Search. If you don’t want to see explicit
content in your search results, you can select *Filter* to block any
explicit content that’s been detected, or *Blur* to blur explicit images.
SafeSearch is set to *Filter* automatically when Google's systems indicate
you may be under 18."
I turned the filter off buut no joy. I think a post from Firefox is more
relevant; gone is the dialogue about warning of unsafe sites with no valid
certificate. They advise they did this to hedge against malware
vulnerabilities. If I am in error please advise of a work around.
Otherwise is a valid certificate for PVE 8.0-x needed PDQ?
If
reply other threads:[~2023-10-30 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC04G9h0iv6+tQ3-=StjZKT+xOaTZY=_zqZf8ELRDx-=JVi9kQ@mail.gmail.com' \
--to=cfytech24x7@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox