1 Topic by zippydan (edited by zippydan 2020-07-20 20:46:31)

  • zippydan
  • Member
  • Offline
  • Registered: 2015-06-25
  • Posts: 26

Topic: errors: fresh install iRedMail 1.3.1 + fresh install Ubuntu 18.04

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.1
- Deployed with iRedMail Easy or the downloadable installer? Downloadable
- Linux/BSD distribution name and version: Ubuntu Server 18.04 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? no
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Trying to do initial setup of iRedMail 1.3.1 on a fresh install of Ubuntu Server 18.04.

These are the relevant errors I'm getting:

First group of errors:

Executing /tmp/apt-key-gpghome.cSWantNEhY/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-key 0x810273C4
gpg: connecting dirmngr at '/tmp/apt-key-gpghome.cSWantNEhY/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
Executing /tmp/apt-key-gpghome.tXbdxKxBA9/gpg.1.sh --keyserver pgp.mit.edu --recv-key 0x810273C4
gpg: keyserver receive failed: No data

Second group of errors:

Get:5 https://packages.inverse.ca/SOGo/nightly/4/ubuntu bionic InRelease [2642 B]
Err:5 https://packages.inverse.ca/SOGo/nightly/4/ubuntu bionic InRelease
    The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 19CDA6A9810273C4
W: GPG error: https://packages.inverse.ca/SOGo/nightly/4/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 19CDA6A9810273C4
E: The repository 'https://packages.inverse.ca/SOGo/nightly/4/ubuntu bionic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Last group of errors:

E: Unable to locate package sogo-activesync
E: Unable to locate package sope4.9-gdl1-postgresql
E: Couldn't find any package by glob 'sope4.9-gdl1-postgresql'
E: Couldn't find any package by regex 'sope4.9-gdl1-postgresql'
<< ERROR >> Installation failed, please check the terminal output.
<< ERROR >> If you're not sure what the problem is, try to get help in iRedMail
<< ERROR >> forum: https://forum.iredmail.org/

Looks like most of the errors are caused when the SOGo repository key isn't retrieved correctly, but I'm also not sure what that last postgresql package error is about.  Can anyone help me clear these errors?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by zippydan (edited by zippydan 2020-07-20 23:30:31)

  • zippydan
  • Member
  • Offline
  • Registered: 2015-06-25
  • Posts: 26

Re: errors: fresh install iRedMail 1.3.1 + fresh install Ubuntu 18.04

I guess I fixed my own problem.

There may have been a firewall issue, since I do have a pfSense firewall in front of iRedMail and I have already setup IPTables on this Ubuntu box to block all except the necessary iRedMail ports and apparently blocking port 11371 might interfere with key retrieval?

Anyway, the objective was to get the key downloaded from somewhere, so I tried all of these:

# curl -sL "http://keyserver.ubuntu.com/lookup?op=get&search=19CDA6A9810273C4" | apt-key add -
# gpg --keyserver keyserver.ubuntu.com --recv 19CDA6A9810273C4
# gpg --keyserver subkeys.pgp.net --recv 19CDA6A9810273C4
# gpg --keyserver wwwkeys.pgp.net --recv 19CDA6A9810273C4
# gpg --keyserver wwwkeys.eu.pgp.net --recv 19CDA6A9810273C4
# gpg --keyserver hkp://pgp.mit.edu --recv 19CDA6A9810273C4
# gpg --keyserver hkp://pgp.mit.edu:80 --recv 19CDA6A9810273C4

These all gave me a bunch of negative results from "No route to host" to "No data".

Finally this command worked, using a combination of a different key server, specifying the protocol to use, and specifying the port to use:

# gpg --keyserver hkp://keys.gnugp.net:80 --recv 19CDA6A9810273C4
# gpg --export --armor 19CDA6A9810273C4 | apt-key add -

-