I have problems setting up a swag docker on my unraid server

[Reikasa_]

Hello smart people,

I want to access my Nextcloud instance, installed on my unraid server over the Internet.
For that I set up a dyndns connection over duckdns. 
I managed to set it up to the point that I reached the swag page at one point, but it seems like it doesn't work anymore...
The documentation I find online is more confusing than helpful to me.
I hope someone here may be able to help me.

some more info:

I set up port forwarding on my router so that requests to the http and https ports get farworded to the ports of swag (8088 , 442)
(there are some weird things going on with my router but the forward seems to work so I don't think it matters)
I'll attach configuration of swag and error the message ( as far as I understand there is a limit of how often I can try changes, but if someone could tell me how to route the traffic to nextcloud, that'd be awesome ) 

I'd be very glad if anyone could help me

all the best

[Catsrules]

I don't believe you can use port 8088 with Letsencrypt. It needs to be port 80 the standard HTTP port. Unless that has been changed it has been a year or so since I have looked at it.

 

Edit,

 

Never mind looks like your using the token validation not http validation. From the error it appears the token might be wrong. make sure it is right.

[Catsrules]

Ignore my first comment, I didn't realize you were using the token validation not http validation for Letsencrypt. Also looks like your getting too many registrations for this IP.

 

From the rate limits of Lets Encrypt, so wait 3 hours before trying again. But it is odd that your getting that. I would think it would be the same account not a different one. (I think accounts are from your email you used to for the registration. If it is the same it should be the same account I would think.

https://letsencrypt.org/docs/rate-limits/

 

Quote

You can create a maximum of 10 Accounts per IP Address per 3 hours. You can create a maximum of 500 Accounts per IP Range within an IPv6 /48 per 3 hours. Hitting either account rate limit is very rare, and we recommend that large integrators prefer a design using one account for many customers. Exceeding these limits is reported with the error message too many registrations for this IP or too many registrations for this IP range.

 

[Reikasa_]

23 minutes ago, Catsrules said:

Ignore my first comment, I didn't realize you were using the token validation not http validation for Letsencrypt. Also looks like your getting too many registrations for this IP.

 

From the rate limits of Lets Encrypt, so wait 3 hours before trying again. But it is odd that your getting that. I would think it would be the same account not a different one. (I think accounts are from your email you used to for the registration. If it is the same it should be the same account I would think.

https://letsencrypt.org/docs/rate-limits/

 

 

yeah I'm going to try again in a few hours. Let's see then