My son and I followed the guide, everything worked beautifully. We updated the realmlist to my Lan IP address (this laptop wll eventually be the server for WoW in the house), started authserver.exe and worldserver.exe... even confirmed the password and user name are correct. But I get this error every time now. Please help! If I add a new login/password to the server and try to log in with that, it still doesn't work. Anyone have any ideas where we went wrong? (oh and yes, this is similar to my last question, but I did not get an answer to that 2 parter).
Related
I'm trying to test a DAG I wrote in Astronomer/Airflow but I'm getting a really peculiar behavior that has me totally stuck.
Airflow's webserver comes up, and then after login as admin it redirects to http://localhost:8080/home which doesn’t appear to exist.
The specific error I get in the browser is ‘too many redirects’. I’m sure something is wrong in my configuration, but it’s not obvious (to me) what. Can you suggest steps for further diagnosis?
Thanks,
Keith
I thought I would share the resolution of this problem in case anyone else encounters it.
This problem came about while developing a DAG to test a part of our pipeline. The repo I was working with used a Dockerfile which was designed for automated testing and was not suitable for a DAG. Once I reverted to the stock Dockerfile the problem went away and I can now load localhost:8080/home just fine.
I have had similar issues when the username or the password is incorrect. I am expecting you are either entering wrong login credentials or your configuration is checking some external authentication server and it is not configured correctly.
I have been working on an intranet site and recently users have been complaining that when they save a change they get "This site can’t be reached." The users are using Chrome exclusively as far as I can tell, and when I tested with Edge, I got no errors. So, I first tested on the web server, I was unable to recreate the issue. I tried on another server within the network and I was also unable to recreate the issue. I then tried my pc, which was connected through a VPN and was finally able to recreate the issue. What is weird is that this just started happening and I haven't updated the site in quite awhile. The can view most pages and the issue only seems to happen when posting to IIS. At this point, I am not sure where to start to troubleshoot this issue. Any help would be appreciated.
Edit: Updated the title to show the actual error I got.
Edit 2: Someone put me on to checking the httperr log and I see an error for the post request with client_reset as the error message. hope that makes the issue a bit more clear.
I found the issue with help from the network security firm the client was using. Once I was able to confirm the issue only occurred when clients who were using a VPN, he ran some tests. The issue was that the firewall was blocking posts that seemed suspicious. Now, this site has been running for years with no issues. My assumption is that they made some security changes and it caused this problem. What was odd, was that I tried a few fixes and they would work for a few times and then would stop working, such as using the site ip address versus the domain name. I hope this helps the next person.
Wade
I've been filtering through google to try to find an answer to this, but I still can't find one that fixes my issue. I have migrated a website to a new server. The framework is Symfony 2.8 on php5.6 using Nginx and PHP-FPM.
Here is a screenshot of the config.php page.
To resolve this, i've tried...
Changing the user for Nginx and php-fpm to both the user I log in with and Nginx, both didn't work
I've opened up the privileges on the cache and log folder to 777 within the app folder, and that didn't work, nope.
I've tried assigning the cache and logs folder to nginx:nginx, no go.
I've manually assigned app.php, app_dev.php, and the console file to have the umask(0000) and umask(0002), nope.
Restarted the Nginx service and php-fpm service after each change, nodda.
I've restarted the entire server thinking something might be stuck, but you guessed it. No!
That leaves me here. I've gone through everything that I can think of and it baffles me that Symfony still won't recognize the directory as writable. It seems like the most simple thing, but... nope.
Anything will help, please pass anything along.
After countless hours of research and scraping the internet for details, I have found the answer! I'm posting it here in case someone else is having the same issue... and hopefully I can save them some time. This took up two days of my life that i'll never get back.
For whatever reason, SELinux was causing this error. I came across this issue on superuser stack exchange, and it told me to temporarily disable SELinux to test. After running sudo setenforce 0 everything came back up. I then completely disabled it and everything has been working fine since.
This happened suddenly and i'm still unsure of the reason. The site worked for about a week before this was triggered.
You should read this to setup you directories permissions http://symfony.com/doc/current/setup/file_permissions.html
I always go for the point 3. with Debian/Apache, Unfortunately i never tried it with nginx.
I have installed kloxo control panel, this is the address http://173.212.227.142:7778/. Then I made domain for my test site, which shows me preview from this link, http://173.212.227.142:7778/sitepreview/kids.com/index.html, which is right.
Now I have installed drupal but it is very hard for me to set here. I have made changes in configuration file like database, and in base_url. But didnot getting the site and it shows me a blank page.Site should come with this address, http://173.212.227.142:7778/sitepreview/kids.com/kids/index.php. I made the base_url as http://173.212.227.142:7778/sitepreview/kids.com/kids.
Please suggest me the solution.
Thanks
If you have a problem in your settings.php file, Drupal won't be able to connect to the database but will show you a page telling you such. The White Screen of Death means there is some kind of php error. It is difficult to know what kind of error from your description. Look in your error logs for php errors and tell us what you see, and it will be easier to help you out.
The white page could be the result of a php error, possibly due to a configuration/setting oversight. You should check your Webservers error log(s) for this, as they might give you some hints on possible causes.
Read this: http://drupal.org/node/158043
Please see my DNN Forum Post for more details.
I've never had any issues with DotNetNuke installations. But with the new v5.20 (or v5.02, whichever it really is), everything runs perfectly fine through installation. I then get to the main default portal homepage. But as soon as I click any of the links available to continue (Home, Register or Login) I get 404 errors every time with a reference back to the applicable aspx page (Home.aspx, Register.aspx or Login.aspx.).
Windows 7, IIS7, SQL Server 2008. All permissions are setup properly on the directory and in IIS. I would think this is an IIS7 configuration issue, but I've tweaked everything in there a half-dozen times. No one at DNN is returning answers on my forum post anymore either after one guy tried.
Help!
This is something to do with the Friendly URL stuff. I found this blog post which talks about the Friendly URL Provider architecture. This made me try changing the urlFormat attribute for the DNNFriendlyUrl provider from "humanfriendly" to "searchfriendly", which made the URLs the way they used to be. I'm not sure exactly where things are going wrong and don't really have time to dig into it at the moment, but hopefully this will be helpful to get you moving again too.
With the release of DNN5 (up until 5.02.01 as of the time of writing), the friendly URL provider won't work when DotNetNuke is not on default port 80. There are different solutions floating around, but the simplest is just to replace the DNN friendly URL provider with the free one from iFinity. The installation is really simple and included in the download. Or see the following blog post:
http://www.sailer.com.au/dotnetnuke/dnn5-friendlyurl-port
Okay have you tried the 'old style' of login - domain.com/default.aspx?ctl=login
If that still doesnt work then i have to say that most likely something has happened to IIS - if so then you might just see if you can install the package you have on a different box or have a friend try a different box
I have done 2 upgrades with 5.2 and a few test installs with the Starter Kit Package and Install packages and have never seen this problem - not to say that it doesnt exist.
My next trial would be to go and redownload the install package from CodePlex and start from scratch to see if you can make the same thing happen again.
OKayone thing I dont think that has been mentioned in reading through everything is double check IIS.
My first guess without looking on your server would be to check if something happened to the 'check file exists' setting - i know this is changed in IIS7 so I cant point to the exact place to check this.
Here is a link to the IIS7 forums on it - http://forums.iis.net/t/1092696.aspx
http://forums.asp.net/t/1191083.aspx
either one might help - google also has a lot on this
Tell me how this goes in checking up on it and we can move forward from there!
you probably need to reg_iis on the version(s) of asp.net that your IIS is going to support.
http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx
If the right version is not set up then you will get the 404 error
So placing it under port 80 works, right?
Is there a good reason not putting it under that port?