Vesta Control Panel - Forum

Hi!
spamcop.net shows the 403 Forbidden error.

I resolve editing /etc/exim4/dnsbl.conf comment the line bl.spamcop.net Restart exim4 and spamassassin services.
While I'm waiting to spamcop resolved the problem

Spheerys wrote: Sun Apr 19, 2020 1:14 pm This tutorial works for me, thanks !

Thank you for contribute on readme file!

grayfolk wrote: Sun Apr 19, 2020 2:43 am

soguor wrote: Sun Apr 19, 2020 2:41 am
I have a server with Nginx+Apache, but should work with only nginx

Sure, i mean you dont need apache config.

I'll update the readme clarify this.

Hi everyone!

I created a repository with templates and instructions to install Jitsi Meet on Ubuntu Server 18.04.

https://github.com/josemyg/vestacp-jitsitemplate

I await your comments.

Any reason for use Nginx+Apache for this? Nginx proxy are enough.


I have a server with Nginx+Apache ...

Hi everyone!

I created a repository with templates and instructions to install Jitsi Meet on Ubuntu Server 18.04.

https://github.com/josemyg/vestacp-jitsitemplate

I await your comments.

Hi everyone!

I created a repository with templates and instructions to install Jitsi Meet on Ubuntu Server 18.04.

https://github.com/josemyg/vestacp-jitsitemplate

I await your comments.

andron_2006_83 wrote: Sat Dec 08, 2018 4:34 pm open file
/usr/local/vesta/data/users/---user_name---/web.conf
find "LETSENCRYPT"
where you want reload LETSENCRYPT
set "no"
resave domain

It's so useful
Thanks a lot!!!:)

I revolved the issue on Ubuntu 18.04 using root:

• Create /backup

• Copy the backup file on /backup

• Run v-restore-user

And worked.

Hi!

I trying install an Docker Image of Collabora Online on Debian 9 and VestaCP Ver. 0.9.8 (Rel. 23) from this tutorial https://nextcloud.com/collaboraonline/ and don't know the correct configuration of the tpl and stpl files. How is the correct configuration?

In the tutorial show this example ...

wildwolf wrote: Mon Apr 09, 2018 5:22 pm

vishne0 wrote: Mon Apr 09, 2018 3:51 pm There are few things I want to know if someone can please reply
1) The hacked server were running ssh on port 22 ?
2) Allow root to login were on?

No to both :-)

Mee too. No to both.