Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - turalyon

Pages: [1] 2 3 ... 14
1
Spanish / Re: Zentyal 7 IDS/IPS no inicia y bloquea tráfico en eth externa
« on: February 08, 2024, 10:15:52 am »
Holap,

Teóricamente, el bug fue solventado en ambas versiones de Zentyal 7 como puedes ver en el siguiente enlace:

* https://github.com/zentyal/zentyal/blob/master/main/ips/debian/zentyal-ips.postinst#L21

Revisa que en el archivo '/etc/init.d/suricata' tienes la siguiente línea de configuración:

Code: [Select]
LISTEN_OPTIONS=" -q $NFQUEUE

Luego, ejecuta los siguientes comandos y vuelve a probar:

Code: [Select]
zs ips stop
systemctl daemon-reload
zs ips restart



This world is ours, and by the Holy Light, we will keep it safe, now and forever.

2
Sometimes, when the network module is restarted by other dependencies, the content of /etc/resolv.conf is lost, and it requires the network to restart by hand.

Code: [Select]
sudo zs network restart

Also, what modules are you using? Can you ping anything? For instance:

- Ping to your router.
- Ping to a public address (8.8.8.8)
- Ping a public domain (google.com)

Finally, you must analyze the network configuration (IP, gateway and DNS), whether the module is enabled or not, the rules from the firewall, if you have the IDS module, you might stop it temporarily, analyze the main log files:

- /var/log/zentyal/zentyal.log
- /var/log/syslog



This world is ours, and by the Holy Light, we will keep it safe, now and forever.

3
Installation and Upgrades / Re: i cant login on Web Interface -
« on: December 04, 2023, 10:53:40 am »
You must debug the issue by analyzing the following log files:

- /var/log/zentyal/zentyal.log
- /var/log/syslog
- /var/log/auth.log
- /var/log/zentyal/access.log
- /var/log/zentyal/error.log
- /var/log/nginx/error.log

Also, I recommend you to enable the debug module as follows:

1. Edit the parameter debug in the log file /etc/zentyal/zentyal.conf
2. Restart the webadmin module to apply the changes.

Finally, did you confirm that the services that manage the webadmin are running?

Code: [Select]
sudo systemctl status zentyal.webadmin-nginx zentyal.webadmin-uwsgi



This world is ours, and by the Holy Light, we will keep it safe, now and forever.

4
Installation and Upgrades / Re: i cant login on Web Interface -
« on: November 20, 2023, 10:49:41 am »
That is weird. Did you try to set (temporarily) a simple password without any special characters to the local administrator like zentyal2023?

Also, did you check the configuration file /etc/passwd ? Did you restart the webadmin module?

Code: [Select]

sudo zs webadmin restart

sudo zs webadmin status


Finally, you might try again to create another local administrator as follows and login to the Zentyal GUI:

Code: [Select]

sudo useradd -m -d /home/zenadmin -G sudo -s /bin/bash zenadmin

sudo passwd zenadmin




“This world is ours, and by the Holy Light we will keep it safe, now and forever".

5
Other modules / Re: Enabling IDS/IPS stops internet on interface
« on: November 16, 2023, 01:03:55 pm »
Hi,

What error are you getting and what version of Zentyal are you using?



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

6
Hi,

Instead of trying to install a package apt install, just upgrade the system using this command apt dist-upgrade.



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

7
Hi,

If the domain controller you want to restore using a configuration backup has additional domain controllers, I do not think it is a good idea because you might break the replication between the domain controllers. In case you do not have other options, just keep in mind that the process might require some work in the ADCs.



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

8
Hi,

If you run the command that is complaining, what is the result you get?

Code: [Select]
wget -T 15 -q --spider https://google.com
echo $?



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

9
Hi,

Samba has the following article that explains how to demote (remove) a domain controller server.

https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

10
Spanish / Re: Nuestro dominio de correo es detectado como spam
« on: August 30, 2023, 01:00:52 pm »
Hola,

Te recomendaría lo siguiente:

1. Revisa tu dominio de correo - incluyendo si tu IP está en una lista negra - usando la web https://mxtoolbox.com/.
2. Revisa los archivos de log, especialmente, el archivo ‘/var/log/mail.log’ para ver si detectas que haya algún usuario enviando correos indiscrimidamente por algún tipo de malware.
3. Implementa las medidas de seguridad adicionales: SPF, DKIM y DMARC.
    - https://doc.zentyal.org/6.2/es/mail.html#securizacion-del-servidor-de-correo
4. Considera en implementar el módulo de Mailfilter.
    - https://doc.zentyal.org/6.2/es/mailfilter.html



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

11
Well, you were able to fix all the packages except one, so it is good news.

The error you get about ‘Element not found’ was reported [here](https://github.com/zentyal/zentyal/issues/2126) and fixed [here](https://github.com/zentyal/zentyal/issues/2121) with version zentyal-samba 7.0.3 you already use.

I guess Zentyal is not fully managing the DNS and DC services and that is the reason you are getting that error. My recommendation is to disable temporarily the DC and DNS modules, then ensure all the related services are stopped, after that, enable again those modules and check if the issue is gone. Finally, you will need to enable its dependencies like the mail module.

The command to get the services and stop them if running - after you disable the modules - are:

Code: [Select]

sudo systemctl status samba-ad-dc named


Two important things to consider before proceeding with the above recommendation:

1. There is a change that after disabling those modules, some of them could not start again due to some issue we do not see yet.
2. You should do a backup now that you can, you can try a configuration backup for that purpose because it will contain your LDAP structure (users, groups, etc) but NO the data like shared folders.



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

12
As you can see, there are several packages that are broken (ii is the right state).

My recommendation is:

1. Do a mark in the following log files before trying to fix those broken packages:
   
   
Code: [Select]
   
    echo ‘#### DEBUGGING’ | sudo tee -a /var/log/dpkg.log
   
    echo ‘#### DEBUGGING’ | sudo tee -a /var/log/zentyal/zentyal.log
   
    echo ‘#### DEBUGGING’ | sudo tee -a /var/log/syslog
   
   
   
2. Try to fix the packages using the mentioned commands.
   
    NOTE: Remember what I said about the fix attempts.
   
3. Monitor the log files from step one in order to identify the issues that might arise when the package is being fixed.
4. Check if any of the broken packages were fixed.

Basically, you must try to fix each package and debug the errors by analyzing the log files and trying again to fix them.

About the Fetchmail error, you can ignore it for now because the Mail module is not correctly installed.



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

13
The update is now available on Zentyal 7 as explained below.

* https://github.com/zentyal/zentyal/issues/2132



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

14
Hi,

Yep, it was a huge mistake xD

If I were you I would do the following:

1. The status of the Zentyal packages that are installed - including half ones -:
   
   
Code: [Select]
   
    dpkg -l | egrep 'zen(buntu|tyal)-’
   
   
   
2. If there are broken packages:
   
   
Code: [Select]
   
    dpkg -l | egrep -v '^ii’
   
   
   

Once you know the status of the packages, you can make a plan, for instance, if there is a broken package, you can try to solve it by running the following command:

Code: [Select]

sudo dpkg —configure -a


NOTE: Sometimes that command must be run a few times until it fixes all the broken packages. Also, in certain cases, you must run to fix the broken packages in a particular order.

Code: [Select]

sudo dpkg —configure zentyal-core

sudo dpkg —configure zentyal-mail


Also, another important thing to do is to analyze the following log files in order to determine if there is a critical error:

- /var/log/zentyal/zentyal.log
- /var/log/syslog

Finally, I recommend you generate a system report and analyze it.

Code: [Select]

sudo /usr/share/zentyal/smart-admin-report


Hope it helps you to recover your Zentyal server.



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

15
Hi,

You cannot upgrade Ubuntu and keep your current Zentyal 5.1 version. Keep in mind that Zentyal needs a specific version of Ubuntu to work, for instance:

- Zentyal 6.x → Ubuntu 18.04
- Zentyal 7.x → Ubuntu 20.04

So, if you want to upgrade Ubuntu, you must use the script ‘/usr/share/zentyal/release-upgrade’ provided by Zentyal.



“This world is ours, and by the Holy Light we will keep it safe, now and forever".

Pages: [1] 2 3 ... 14