Storage conf file:
nfs: NAS
export /volume1/Storage
path /mnt/pve/NAS
server 192.168.50.100
content images,vztmpl,rootdir,iso,backup
maxfiles 2
options vers=3,async,noatime,fsc,nodiratime
Sorry, that should be:
options vers=4,async,noatime,fsc,nodiratime
I'm
Hi,
I have a Synology with High Availability serving NFS storage to Proxmox.
A couple of months ago, this started happening:
Apr 24 12:32:51 proxmox-1 pvestatd[3298]: unable to activate storage
'NAS' - directory '/mnt/pve/NAS' does not exist or is unreachable
Apr 24 13:08:00 proxmox-1
I did that as part of the migration
Serial driver? Don't have have any odd devices showing up in the device
list
On 4/24/2019 2:02 PM, Mark Adams wrote:
Haven't tried this myself, but have you updated the qemu-agent and serial
driver to check it's not that?
On Wed, 24 Apr 2019, 18:59
Haven't tried this myself, but have you updated the qemu-agent and serial
driver to check it's not that?
On Wed, 24 Apr 2019, 18:59 David Lawley, wrote:
> I know, its an oldie, but.. Windows Server 2003
>
> But since moving it to PVE 5.4 (from3.4) its does not reboot/restart on
> its own. You
I know, its an oldie, but.. Windows Server 2003
But since moving it to PVE 5.4 (from3.4) its does not reboot/restart on
its own. You can select a restart, but it does not. You have to start
it manually.
Migration from 3.4 was done via backup then restore into 5.4
Poking around, but if
https://bugzilla.proxmox.com/show_bug.cgi?id=2187
Thanks.
--
Mark Schouten
Tuxis, Ede, https://www.tuxis.nl
T: +31 318 200208
- Original Message -
From: Thomas Lamprecht (t.lampre...@proxmox.com)
Date: 24-04-2019 13:38
To: Mark Schouten (m...@tuxis.nl), Dominik Csapak
Am 4/24/19 um 1:26 PM schrieb Mark Schouten:
>
> The goal would indeed be to be able to limit the less secured users to
> specific source addresses. At this moment, we managed to limit API-calls by
> looking for the X-requested-by header, combined with the API URL with an
> exclude for novnc,
The goal would indeed be to be able to limit the less secured users to specific
source addresses. At this moment, we managed to limit API-calls by looking for
the X-requested-by header, combined with the API URL with an exclude for novnc,
but the user is still able to login to the web
Am 4/24/19 um 12:19 PM schrieb Mark Schouten:
>
> Hi,
>
> Sorry, that doesn't answer my question. I want users that have 2FA to be able
> to use the GUI, and I want to be able to disallow the GUI for certain users.
> I know that the GUI just uses the API as a backend.
That's not possible,
Hi,
Sorry, that doesn't answer my question. I want users that have 2FA to be able
to use the GUI, and I want to be able to disallow the GUI for certain users. I
know that the GUI just uses the API as a backend.
By 'do not allow access to /', do you mean for the user, or at a HTTP-level?
On 4/24/19 11:54 AM, Mark Schouten wrote:
Hi,
we want all users to authenticate using 2FA, but we also want to use the API
externally, and 2FA with the API is quite difficult.
In the latest version, you can enable 2FA per user, but you cannot disable GUI
access for e.g. API users. So a API
--- Begin Message ---
Due to a death in the family I am out of the office. Assistance is available
via phone or E-mail 24 hours a day by contacting support. The support E-mail
address is supp...@gmail.com. Many of the things that you may have needed my
assistance for can be directed to Wesley
Hi,
we want all users to authenticate using 2FA, but we also want to use the API
externally, and 2FA with the API is quite difficult.
In the latest version, you can enable 2FA per user, but you cannot disable GUI
access for e.g. API users. So a API user can just login without 2FA. Is there a
13 matches
Mail list logo
