-
Notifications
You must be signed in to change notification settings - Fork 356
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
zappa certify → AttributeError: 'NoneType' object has no attribute 'split' #1302
Comments
I created the DNS name and I'm getting the same error:
|
Curiously, even though I got an error, it works! |
Update: if you are using AWS certificate manager but not using route53, this needs to be added to the json file:
I added that, and now it works:
But another domain is giving this error:
However, even though I got the error, the system is now working. |
I haven't used the certify or domain features. |
I will give you a PR with marginally improved documentation. I haven't figured out enough to understand why I'm sometimes getting errors and sometimes not getting errors. It's confusing. |
Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed. |
Hi there! Unfortunately, this Issue was automatically closed as it had not seen any activity in at least 100 days. If the Issue is still relevant to the latest version of Zappa, please open a new Issue. |
I'm trying to set up zappa to use a private domain (
aws-lambda.digitalcorpora.org
). Myzappa_settings.json
file (below) specifiesus-west-2
as the region, although I have put the certificate in both us-west-2 and in us-east-1 (since Zappa didn't like the cert in the us-west-2 region).zappa certify
produces a stack trace.zappa_settings.json:
Stack trace:
Expected Behavior
It should certify.
Actual Behavior
Stack trace.
Possible Fix
Right now the
aws-lambda.digitalcorpora.org
doesn't exist. I just made this a CNAME tock9qrzfy5l.execute-api.us-west-2.amazonaws.com
which is my service address for the lambda (which is working). The instructions at https://github.com/zappa/Zappa don't mention what I should do regarding DNS, BTW.Your Environment
version
command.) 0.58.0pip freeze
:zappa_settings.json
:The text was updated successfully, but these errors were encountered: