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

[BUG] Squarespace support after Google Domains acquisition #486

Closed
1 task done
DevDema opened this issue Jun 11, 2024 · 5 comments
Closed
1 task done

[BUG] Squarespace support after Google Domains acquisition #486

DevDema opened this issue Jun 11, 2024 · 5 comments

Comments

@DevDema
Copy link

DevDema commented Jun 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Recently, Google Domains was acquired by Squarespace.

The existing documentation and ini files display instructions for Google Domains, but they have not yet been updated to Squarespace.

The current access token I used to have for Google Domains, gives out 400: Bad request when trying to use it:

Unable to rotate DNS challenges: 400 Client Error: Bad Request for url: https://acmedns.googleapis.com/v1/acmeChallengeSets/###:rotateChallenges

Expected Behavior

We should be provided in the docs and in the ini files some instruction on how to setup a domain registered on Squarespace.

Steps To Reproduce

  1. Have a domain registered on Google Domains
  2. Generating an API_KEY on Squarespace with the same properties for Google Domains does not work

Environment

- OS: Ubuntu Server
- How docker service was installed: Docker Compose

CPU architecture

arm64

Docker creation

version: "2.1"
services:
  swag:
    image: lscr.io/linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Rome
      - URL=###
      - SUBDOMAINS=###
      - VALIDATION=dns
      - dns_google_domains_access_token=###
      - dns_google_domains_zone=###
      - CERTPROVIDER=letsencrypt
      - DNSPLUGIN=google-domains
      - EMAIL=###
      - ONLY_SUBDOMAINS=false

Container logs

swag  | dns validation via google-domains plugin is selected
swag  | Generating new certificate
swag  | Saving debug log to /var/log/letsencrypt/letsencrypt.log
swag  | Requesting a certificate for #### and 3 more domains
swag  | Unsafe permissions on credentials configuration file: /config/dns-conf/google-domains.ini
swag  | Encountered exception during recovery: certbot.errors.PluginError: Unable to rotate DNS challenges: 400 Client Error: Bad Request for url: https://acmedns.googleapis.com/v1/acmeChallengeSets/###:rotateChallenges
swag  | Unable to rotate DNS challenges: 400 Client Error: Bad Request for url: https://acmedns.googleapis.com/v1/acmeChallengeSets/####:rotateChallenges
swag  | Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
swag  | ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/google-domains.ini file.
⏺ docker-
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@wxianxin
Copy link

Second this issue. If there is no plan on supporting square space, could some one suggest a service provider that I should transfer the domain to?

@thespad
Copy link
Member

thespad commented Jun 16, 2024

@martinmiglio
Copy link

martinmiglio commented Jun 16, 2024

suggest a service provider that I should transfer the domain to?

Using another service's name servers would suffice without a full domain transfer, like cloudflare or route 53.

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

5 participants