Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script does not print the DNS records #259

Closed
arnpatel opened this issue Jan 31, 2023 · 4 comments
Closed

Script does not print the DNS records #259

arnpatel opened this issue Jan 31, 2023 · 4 comments

Comments

@arnpatel
Copy link

Hello, I just ran this script today on a fresh Debian 11 instance. It installed the required utilities for the mailserver but never printed the DNS records at the end. It also did not create a file called dns_emailwiz to save the records. I ran the script as root. Any thoughts on could be wrong here?

Arth

@LukeSmithxyz
Copy link
Owner

LukeSmithxyz commented Jan 31, 2023 via email

@arnpatel
Copy link
Author

It runs as normal trying to install and configure the utilities, and then stops at this output:
...
Unpacking opendkim-tools (2.11.0beta2-1) ...
Setting up opendkim-tools (2.11.0
beta2-1) ...
Processing triggers for man-db (2.9.1-1) ...
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)

I am thinking it never gets to the end of the script where you echo the DNS entry variables. FYI - I already set up SSL cert before running the script. Maybe a recent commit broke something?

@arnpatel
Copy link
Author

Found it, on line 70, the 'esac || exit $1' command tries to exit the script with the exit status passed as argument $1, only if the previous case statement has failed. And somehow the SSL code block is failing. You need to check the lines 51-70 again. I removed '|| exit $1' for debugging, and the script worked as expected.

esac || exit $1

@LukeSmithxyz
Copy link
Owner

The $ is definitely a typo, but I don't think it should've failed anyway.

Did you get your SSL with certbot or some other service?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants