I've been using Lightsail with the same account for over 2 years now. I have been running 3 instances without any issues, up to now. I had to reboot one of the instances, but I got an error "It looks like you aren't authorized". I'm using the root acccount, not an IAM account (but I tried to make one and that didn't work either). I'm logged into the root account that I've also used to create and manage all the instances in the past. So I don't see why I wouldn't be authorized. I'm not late on payments, and I don't have any errors or other issues anywhere that I know of.
I also tried to just create a new instance (I thought it may have been a problem related to the instance itself), but this gave me an error: "Sorry, you've reached your maximum limit of Lightsail Instances : 0". I have 3 instances, 2 of which are currently running and still accessible. Could this be a setting somewhere that I've missed? Or is this more likely to be an issue with my account that needs to be fixed on Amazon's end?
Related
i have a redis instance which is installed as a linux service. I have created few users with some RBAC policies. Everything works fine as expected for few days, but suddenly all my newly created users get deleted due to which my application connecting to redis is throwing exception.
Also, no other person can access this server except me.
Can someone help me how to persist the newly created users in redis for lifetime?
Everything works fine as expected for few days, but suddenly all my newly created users get deleted
After ruling out other trivial reasons (connecting to the wrong instance, for example), I believe your Redis service was simply restarted for some reason, perhaps after a server restart.
Once an ACL rule is created/modified/updated, the configuration needs to persisted to a file to make it survive a Redis restart; to do that, run either:
CONFIG REWRITE, if you are specifying your ACL users / rules inside your main configuration file (the default option);
ACL SAVE, if you are using an external ACL file.
To learn more about how Redis deals with ACLs, be sure to check out the official documentation.
Its a pity google does not offer its domain service in Germany, otherwise launching a react website vial firebase would really be super easy, great service!
The only problem I faced is that the SSL generation seam not to work as described in the documentation.
In Firebase Hosting it keeps on saying: Needs setup
And the documentations says on that topic:
In most cases, your DNS A records haven't propagated from your domain
name provider to Firebase Hosting servers. Troubleshooting tip: If
it's been more than 24 hours, check that you've pointed your records
to Firebase Hosting.
By pointing the records I assume they mean adding two A Type files with provided IP´s.
I added those more than 24 Hours ago and they are as valid as they can be, I checked them multiple times now on my DNS provider checkdomain.de.
Or am I getting something wrong here?
Thanks for any help!
Ok, the problem was that the provider had an additional field outside of the "repository scope" which was titled main IP. This IP also translated into a A entry which could be discovered by the prompt suggested by #FrankvanPuffelen (thanks for that):
dig +noall +answer <your-domain-name>
One the field value has also been changed to one of the IP's provided by firebase the SSL Certificate has been successfully generated.
I hope that it does help someone else in the same situation and I'll try to convince firebase support to add those hints to the documentation.
I had an issue with my server that hosts RavenDB. It was running out of hard drive space. I cleared up some space by deleting a few databases that were no longer in use (through the management portal). I then shut down the RavenDB service. I deleted the data from the "PeriodicBackup-Temp" folder in the directory for one of the databases, and restarted the server. When the server restarted, I was getting errors from any site that tried to connect to any of the databases (503 server error). I debugged the error, and found that it is happening when I create the document store. Specifically:
IndexCreation.CreateIndexes(new CompositionContainer(new TypeCatalog(types)), docStore);
Now, the thing is, I haven't changed any code on these sites in a long time, and I certainly haven't changed anything to do with connecting to RavenDB or creating indexes. Here is what the error said:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
For a while, I was also getting errors in the management portal that said that whichever database I was currently looking at did not exist (which was odd, since I was looking at the documents in the document stores while it was telling me the database did not exist...)
It's now four hours later. I have noticed all of the sites except two have started working at some point. I was hoping that Raven just needed to rebuild indexes, but when I look at the databases that correspond to the sites that are still throwing the error, Raven says that there are no stale indexes.
I am using build 2750. I have been using this build for over a year if I remember correctly.
All of my sites use the exact same code base. They are hosted on different sites and connect to different databases, but other than that they are exactly the same. I'm pretty confident that this issue has something to do with the database server, and not the web server.
Right now, the sites are not getting used, so it's not a load issue. The RavenDB process isn't even using any CPU except occasionally.
Any ideas what could be causing this? I hate to just "hope" that it's going to start working in a few hours, but it's all I have at this point.
After waiting about 8 hours, those two sites were still unable to connect. I restarted those websites, and everything started working again. This is something I had tried earlier, so I don't know exactly what needed to complete before restarting the site had an affect. I am completely up and running again. If anyone can shed some light on why this fixed it, I'm all ears.
Some users trying to visit my website are getting a warning explaining "This is probably not the site you are looking for".
One of them sent me a screenshot (I'm sure we've all seen this screen before at some stage):
I'm using an SSL cert signed by StartSSL. It's signed for shareshaper.com and www.shareshaper.com.
You can see that the screenshot says that the user attempted to reach www.wamrc.com. I've never heard of that site before. For some reason though, when I visit www.wamrc.com I end up on my staging server.
I've tested my SSL setup with a number of online testing sites and they all report that everything is fine. I can't seem to replicate the issue myself.
What could be causing this error?
Some Other Thoughts
I have another StartSSL certificate I use on my staging server. This one is valid for staging.shareshaper.com and (I assume, can't quite remember) shareshaper.com.
One user who get the warning was using iPad Safari. Another OS X Chrome.
wamrc.com appears to belong to some dude called Oscar Arbelaez.
The issue was initially reported in this Reddit thread
For example it could be an incorrect DNS A-record for www.wamrc.com (pointing to your IP), or an incorrect cname for the same one, but all this is essentially included in the message in the screenshot.
Your server is misconfigured. Its reporting itself as www.wamrc.com.
You need to talk to your hosting provider.
I've been trying to research this for hours now, and I can't find any related articles.
I have an installation of MediaWiki that is under SSL and uses an extension of the AuthPlugin to authenticate users to an external database upon their login.
If I access the wiki without being logged in, I can see the content that anonymous users would see just fine. If, however, I log into the site, the wiki is no longer available, and only brings up a 500 Internal Server Error.
I've checked the error logs, and nothing shows up there corresponding to the bad request.
On a staging server, I have the same codebase running under non-SSL, and I do not encounter any issues when logged in, so I'm thinking there might be something to do with tthe combination of SSL and the AuthPlugin.
Anyone out there encounter similar using extensions of AuthPlugin under SSL?
Thanks!
Start by turning on PHP debugging and logging, so you can actually see the error instead of having to guess what the 500 means:
http://www.mediawiki.org/wiki/Manual:Errors_and_symptoms#MediaWiki_Errors
I ran into this same issue for one wiki user after an upgrade. All other wiki users could still log in. My issue was due to the user using a skin that did not work. After changing the user's skin to Vector(default) he could log in again. I couldn't figure out how to change another user's preferences as an Admin, so I ended up running an update statement to the mysql database. Hope this helps someone else.