Antsle Forum
Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more.
Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked.
Doesn't look like you can re-issue a new InstantSSL from anthill
I resurrected an old box and am trying to change the IP address of the old anthill entry. I've tried everything from completely removing my anthill entry to changing to a completely new InstantSSL domain. Nothing. It always seems to go back to the original domain name, and original IP address, no matter what I do.
How can I *entirely* wipe out my domain name on anthill and start over? At this point, I just want it to work.
Also, are there any known issues or concerns with going from 0.11.1c directly to (the current) 2.x version via command line?
Thanks,
Bruce
So the DNS change finally propagated around, so it looks like a complete wipe and start over (somewhat) worked.
However, now I have a different problem. At fairly random times, if I go to the domain entry version (xxx.antsle.us:3000), I get:
exceed max line 4096
That's all I get on the page. Yet if I go there directly via IP (xx.xx.xx.xx:3000), it has zero problems and works finally. Any ideas?
Also, I'm still interested if I can upgrade directly from 0.11 to 2.0...
Maybe something in the nginx config file? /etc/nginx/nginx.conf
http://nginx.org/en/docs/http/ngx_http_core_module.html#large_client_header_buffers
I don't think they've release the upgrade to 2.0.0 yet (I've been looking every day!)
Hmmm. Might be a cache issue. Doesn't have a problem in Incognito mode. Interesting that the other ports (i.e., anything not 3000) still work fine, but just 3000. Still working on it.
Quote from lancem on April 12, 2020, 4:17 pmI don't think they've release the upgrade to 2.0.0 yet (I've been looking every day!)
I just upgraded to edgeLinux 0.12 (which brought along with it, AntMan 2.2.0g), so the update appears to have worked fine from 0.11.1c. I sort of just took a chance, but it worked fine.
Also - SOLVED - appears to be a cache issue of some sort. I went to chrome://settings/siteData, searched for antsle.us, and removed all data. Now I have no problem with the domain name. Go figure.