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 ... 3 4 [5] 6 7 ... 14
61
Spanish / Re: Actualizacion a Ubuntu 20
« on: November 30, 2022, 10:16:36 am »
Holap,

Las actualizaciones de versiones han de ser realizaras desde Zentyal, de lo contrario el servidor quedará inestable y será necesario realizar un rollback.

Si estás usando Zentyal 6.2 (Ubuntu 18.04), puedes actualizar a Zentyal 7.0 (Ubuntu 20.04) sin problemas siguiendo la siguiente guía. En caso de que te refieres actualizar a Ubuntu 22.04, todavía no es posible.

* https://doc.zentyal.org/es/upgrade.html

--

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

62
Hi,

Apparently, you did not configure a virtual mail domain in 'Mail -> Virtual Domains' as the following link explains.

  * https://doc.zentyal.org/en/mail.html#creation-of-email-accounts-through-virtual-domains

As soon as you create the virtual mail domain (the mail module must be enabled) you will be able to create the email address in the domain user as the above link explains.

When the mail module is enabled, the virtual mail domain is created as well as the email in the domain user, you will be able to login in Sogo and see the user's mailbox.

--

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

63
Hi,

If you are not using the DNS module, then you need to set your network configuration from the following tabs:

* Network -> Interfaces
* Network -> Gateways
* Network -> DNS

As soon as you enable the network module and save changes, Zentyal should configure your server's network. In case of an issue, as always, you will need to analyze the 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".

64
Installation and Upgrades / Re: Fresh Install - Certificate Problem
« on: November 29, 2022, 11:32:19 am »
It looks like Zentyal interpreted the hostname and domain that your server had incorrectly.

I don't think you will have more issues with this again in that machine at least.

--

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

65
Installation and Upgrades / Re: Fresh Install - Certificate Problem
« on: November 28, 2022, 03:34:35 pm »
Hi,

It seems that your domain name is too long:

Code: [Select]
asn1 encoding routines:ASN1_mbstring_ncopy:string too long

How many characters it has? Can you tell me an example? Apparently, this behavior is not considered by Zentyal.

--

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

66
Installation and Upgrades / Re: Fresh Install - Certificate Problem
« on: November 28, 2022, 11:01:22 am »
It is a strange behavior, the other day I tested the script for an internal test and everything worked correctly. Did you check if you have some broken package or any error in the log file '/var/log/zentyal/zentyal.log'?

As you said, you can create a self-certificate file and set the right permissions so you can use the Zentyal GUI.

--

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

67
Hi everyone,

so I had (needed) to install another Zentyal 7 from scratch. Started with installing Ubuntu 20.04 Server and then followed the .sh script from zentyal.com.

All was well to where the script attempts to install suricata repo. This has already been reported number of times, where the repo can't be added by the script due to incorrect/lack of signature.

My question here is, could we change the script to include suricata PPA installation as per:
https://suricata.readthedocs.io/en/latest/install.html#ubuntu

After the cli installation finished I wen't to the admin page and continued with the configuration.

Installer hang on 53% with "saving network module" but because I've seen it previously I just let it run (long enough to finish a cup of tea). Then pointed the browser to the new IP and I was "again" welcomed with Configuration Wizard. I skipped it completely and when the website reloaded all was working fine.

This is a VM hosted on proxmox so the IP change during installation isn't much of a problem, plus I already knew this will happen.
I've managed to connect this server as an additional domain controller. All went smooth, with AD syncing without any problems.

Second question in this place relates to DNS... I see no DNS sync between dc01 and the new machine. Does this mean I have to manually copy DNS entries if I want some resilience or is there a way to make it automatic?

Cheerio!

Hi,

You should create an issue or Pull Request in Github with the Suricata issue or improvement (the PPA you mentioned).

Regarding the DNS sync between domain controllers, Zentyal updates the zone using the 'samba_dnsupdate' command, so, if the replication between domain controllers is working correctly, any DNS record added by one of the two DCs, should be synced to the other.

* https://wiki.samba.org/index.php/Verifying_the_Directory_Replication_Statuses

Also, keep in mind that Zentyal only displays in the GUI the DNS records created by hand in the GUI itself, the rest of the records must be queried using the CLI.

* https://wiki.samba.org/index.php/DNS_Administration#Listing_zone_records

--

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

68
Hello
I have same issue with saving modules status
Fresh install of Zentyal 7.0, only basic modules added (ex. doman controller and file sharing).
when saving changes in modules configuration - it is endless (waited few hours).
I have made 2 separate installtions to be sure, on 2 separate computers. Always the same situation.
I will try to install 6.x and upgrade to 7 to see results.

This behavior is caused by the following bug:

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

69
Hi,

1. Configure always the new servers as an Additional Domain Controller, otherwise, the service will be configured from scratch. And do not change the Domain mode in Zentyal or you will lose everything (it removes everything and configured from scratch).
2. You have to migrate the FSMO roles, below you have the link that explains it.
 * https://wiki.samba.org/index.php/Transferring_and_Seizing_FSMO_Roles
3. Once you confirmed that the join was successful and the replication between both servers works as expected, you can remove the 'old' Zentyal and if you wish, migrate the FSMO roles to the new Zentyal 7.0 server.
 * https://wiki.samba.org/index.php/Verifying_the_Directory_Replication_Statuses
 * https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record
 * 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".

70
Installation and Upgrades / Re: Error after update Zentyal 7.0
« on: October 31, 2022, 11:55:41 am »
Hi,

Did you check if you have any broken packages after the upgrade?

Code: [Select]
sudo dpkg -l | egrep -v '^ii'

Did you analyze the log files?

* (mainly) /var/log/zentyal/zentyal.log
* /var/log/zentyal/error.log
* /var/log/syslog

Also, did you tried to restart the Webadmin module?

Code: [Select]
sudo zs webadmin restart

In case if fails, analyze the log files and the status of the following services as well:

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

Hope it helps.

--

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

71
Hi,

I tried to install Zentyal in AWS yesterday I did not have any issues. Below you have a few things I did:

* I create a Network Interface in AWS and set there a static IP (10.0.10.20).
* My Security group allows IMCP (echo request), SSH, 8443/TCP.
* The instance has an Elastic IP associated.
* The EC2 instance has the following settings:
  * Ubuntu Server 20.04 LTS (HVM), SSD Volume Type
  * Architecture 64-bit (x86)
  * Instance type: t3a.medium
  * Public subnet
  * Network interface created previously

And for the Zentyal, I installed it without GUI using the following script.

  * https://doc.zentyal.org/es/installation.html#instalacion-sobre-ubuntu-20-04-lts-server-o-desktop

Regarding the initial configuration, after login for the first time, I just installed the firewall module so I could configure the Network, which I set the following:

  * Internal
  * IP: 10.0.10.20
  * Netmask: 255.255.255.0
  * Gateway: 10.0.10.1
  * DNS: 8.8.8.8 , 8.8.4.4
 
Once I saved the changes, everything was working correctly, even after rebooting the server.

I hope this helps you.

--

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

72
Installation and Upgrades / Re: missing zentyal
« on: October 27, 2022, 04:08:27 pm »
Hi,

That is not the way Zentyal must be upgraded from 6.2 to 7.0. You need to do a rollback and then, follow the following link.

* https://doc.zentyal.org/en/upgrade.html

--

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

73
Directory and Authentication / Re: zentyal no longer seeing KDC servers
« on: October 21, 2022, 04:05:34 pm »
Hi,

The domain controller is missing in the output you provide. Basically, the following function must be executed so I can see if something is wrong with the domain controller module.

* https://github.com/zentyal/zentyal/blob/master/main/core/src/scripts/smart-admin-report#L194

--

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

74
Other modules / Re: VPN suddenly stopped working - Zentyal 6.0
« on: October 21, 2022, 04:01:48 pm »
Hi,

No, really. You just need to create a dummy certificate so the CRL file is updated. Once you did that, the issue should be fixed for now. However, it will happen again if in 30 days you do not perform any action with some certificate, so the CRL will expire again.

--

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

75
Hi,

It looks like the actions you did are right. The Network configuration should be:

* Type: Internal
* IP: 172.31.92.23
* Subnet: 255.255.240.0
* Gateway: 172.31.X.X
* DNS: X.X.X.X

What modules do you have installed and enabled? Did you check if you are not blocking yourself with the firewall module?

Finally, did you try to connect to the EC2 instance using AWS EC2 Serial console when you lost the connection?

--

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

Pages: 1 ... 3 4 [5] 6 7 ... 14