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

Certificates not reacheable / available for AdGuard addon #518

Closed
deam0n opened this issue Jan 14, 2024 · 6 comments
Closed

Certificates not reacheable / available for AdGuard addon #518

deam0n opened this issue Jan 14, 2024 · 6 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@deam0n
Copy link

deam0n commented Jan 14, 2024

Problem/Motivation

Adguard needs access to the certificate in order to have SSL implemented.

Expected behavior

Configure adguard to fetch fullchain.pem and privkey.pem from /addon_configs/a0d7b954_nginxproxymanager/letsencrypt/live/npm-1/ and be able to retrieve the certificates

Actual behavior

adguard cannot retrieve the certificates and displays the error: reading cert file: open /addon_configs/a0d7b954_nginxproxymanager/letsencrypt/live/npm-1/fullchain.pem: no such file or directory

Steps to reproduce

Create a npm with ssl certificates, configure adguard to use it.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

@deam0n
Copy link
Author

deam0n commented Jan 31, 2024

Since no solution seems to be found, I'll revert back to last version of the add-on where this was working as expected..

@renaiku
Copy link

renaiku commented Jan 31, 2024

@deam0n the solution has been provided here hassio-addons/addon-bitwarden#294

Don't use nginx as a cert provider, you should use let's encrypt addon for that.

@deam0n
Copy link
Author

deam0n commented Jan 31, 2024

@deam0n the solution has been provided here hassio-addons/addon-bitwarden#294

Don't use nginx as a cert provider, you should use let's encrypt addon for that.

I'm not using this addon uniquely as a cert provider.

I'm using this addon to create a SSL NPM. Meaning that I create a host and let the addon create the certificate for it as well. This is purely a FS permission issue I guess...

Furthermore, this addon requires the port 443 to be redirected to it, and let's encrypt addon as well so I cannot use both addons.

Copy link

github-actions bot commented Mar 2, 2024

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Mar 2, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 9, 2024
@blair287
Copy link

@deam0n the solution has been provided here hassio-addons/addon-bitwarden#294
Don't use nginx as a cert provider, you should use let's encrypt addon for that.

I'm not using this addon uniquely as a cert provider.

I'm using this addon to create a SSL NPM. Meaning that I create a host and let the addon create the certificate for it as well. This is purely a FS permission issue I guess...

Furthermore, this addon requires the port 443 to be redirected to it, and let's encrypt addon as well so I cannot use both addons.

Did you find any solution I found the ssl certs in addon_configs folder but adguard won't accept that file path. Seems no one is interested in hearing our issue I'm using npm to handle the the dns.

Letsencrypt addon won't work as npm is already using the ports so I have no idea how to solve this issue now other than copy and paste them every 3 months

@deam0n
Copy link
Author

deam0n commented Mar 21, 2024

@deam0n the solution has been provided here hassio-addons/addon-bitwarden#294
Don't use nginx as a cert provider, you should use let's encrypt addon for that.

I'm not using this addon uniquely as a cert provider.
I'm using this addon to create a SSL NPM. Meaning that I create a host and let the addon create the certificate for it as well. This is purely a FS permission issue I guess...
Furthermore, this addon requires the port 443 to be redirected to it, and let's encrypt addon as well so I cannot use both addons.

Did you find any solution I found the ssl certs in addon_configs folder but adguard won't accept that file path. Seems no one is interested in hearing our issue I'm using npm to handle the the dns.

Letsencrypt addon won't work as npm is already using the ports so I have no idea how to solve this issue now other than copy and paste them every 3 months

nop.. I just reverted back to the previous version of the addon. #sad

@github-actions github-actions bot locked and limited conversation to collaborators Apr 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

3 participants