Search results

What what be your recommendation for running a Docker on Proxmox VE? Run it in a VM or in an LSC container?

Thanks, that's why I checked. Remove instead of autoremove should be fine than right?

I moving my NAS away from the proxmox host to a container. Therefor I am deleting samba, nfs-common, and nfs-kernel-server packages. For Samba I used 'apt-get autoremove samba', which went fine. For NFS I used 'apt-get autoremove nfs-common nfs-kernel-server', but it prompts me for the below...

For completeness of post and help others. The turnkey appliance does still require to adjust host file on server to remove cURL error. But there are no errors on the block editor at all, i.e. works out of the box.

As earlier explained above, adding to the host file works for cURL from command line. Related error to cURL in WP disappears both block editor still has error. I delete the entire container and put turnkey wordpress in place instead. Works great.

If you mean wether the container has a direct public IP, no. My router forwards the public IP to the container local IP.

NSlookup from the container also fine, i.e.: root@ct-db10-wordpress:/etc/apache2# nslookup mydomain.com Server: localip Address: localip#53 Non-authoritative answer: Name: mydomain.com Address: mypublicip The blockeditor of WP is connecting via cURL... Command line curl...

I used the DNS server of the PVE host which in turn uses the DNS of my internet provider. Ping mydomain.com is actually fine resolved from the WP container. Cannot find how to manual adjust the address cURL uses?

Port 80 is open, i.e. in can reach the site on it's domainname at port 80 and it redirects. 'Or the domain can't be resolved' to the local WP, that's why I tried to add 'local ip domainname' entry in the /etc/hosts file, but that doesn't work either.

I get the following error in my Wordpress LXC container. I think it has to to with the container but don't know who to solve it. I tried to add 'local ip mypublicdomain.com' in the /etc/hosts file of the container but that doesn't help. The adjustments are also overwritten after reboot. Also no...

I want to hook up a container with a webserver to the internet. The container is hosted on PVE together with vm's and containers not hooked up to the internet. I am wondering how I can best configure my container to publish it to the internet and isolating it from my other VM's and containers. I...

Not sure where to post this but I would like to share a product idea for which I think for which the technology is already present in Proxmox VE. I currently miss a web-based SSL VPN in the open source space, something like SSL Explorer in the past. The product should basically provide: - Strong...

Thanks again, understand. Definitely not a path to pursue further.

Thanks Oguz, backup is indeed also a solution. Based on you answer I assume there is no solution to place or redirect /etc/pve and /var/lib/pve-cluster/config.db to a location on the ZFS storage?

When I setup my new server: - I installed Proxmox VE on a fast SSD disk (default partitioning, probably ext4) - And for ISO's, vm disks, and container disks, and data I created ZFS pool of HDD disks and datasets on the same server. But how can I put my configuration files, i.e. vm and container...

Thanks, was starting to get worried :-).

I don't understand why Proxmox indicates that my SSD which I basically only used for the Proxmox OS and application (PVE) itself and not for e.g. storage of ISO, VM's or data is for 98% in use. It's a 1 TB SSD NVM disk. On the local (LVM) only two machines are stored of respectively 32 GB and 16...

Saw more NFS issues related to the upgrade to PVE 6.2.4.. But no conclusive answer or solution. What’s the status on this?

Confirmed here when upgrading from to one version ealier to 6.2-4. Strange thing is that one of my NFS shares shared on Proxmox still works and the other one not.

Very strange I had two perfect working ZFS datasets shared through NFS and one of the two suddenly says when mounting from Ubuntu Desktop 'operations permitted for root only'. ZFS properties are set the same for both datasets, except the dataset not available through NFS is an encrypted dataset...