First question posted, apologies if it's been answered, but I have been searching for hours and can not seem to find the answer.
I developed a new version of my site on a sub domain and then set it live by moving it up to the domain itself -- a Drupal 7 site.
Apart from a couple of glitches everything went smoothly, I changed the settings.php to point to the correct base url, changed .htaccess etc, all hunky dory.
The one thing that is not working is account creation, either by the user themselves or by admin. I have checked permissions, all OK. No errors in logs. The live site is forced to use the https protocal, reverted it back to http, no joy. I read somewhere that the metatab module sometimes causes issues, I disabled it, again no joy.
I have an action that sends users a bespoke welcome email when admins create their account... This was working perfectly under the sub domain.
Got to the bottom of this, I had over ridden the form_submit hook for user registration. Odd how it worked before...
Fixed
Related
We have moved our website which uses typo3 from on-prem to Azure cloud. We setup a Front door with firewall protection which is different from the previous setup.
Since day one when I log in I can do some stuff for a short while (like 4-5 minutes) and then it kicks me out to login screen.
Another example is when I'm logged in, I open a new tab and check some other sites then go back to typo3, again I'm logged out. Need to log in again.
I lost some of my posts while adding some additional info from other websites.
Any ideas?
I had a similar issue. I resolved it with replacing lockIP in the install tool from 4 to 0.
Note, this is a temp solution so you can keep working, but you really need to find out why this is happening.
Best regards
For some reason I have yet to discover, I cannot login to my Drupal website any more.
Attempts to do so result in loading my user page (as usual), but it is shown as if I still were a guest.
This is the case for any user I try to log in with.
No problems with passwords. No blank pages of death. Everything goes just fine except for the fact that the login is not affective: admin pages are still 403 forbidden and there is no admin bar.
Any thoughts?
I already tried clearing the cache and repairing the sessions table.
And it got solved. Some bright mind suggested restarting the MySQL server Drupal was running on. That did the trick, though I don't understand why.
Our website has been recently hacked (Joomla 1.5, hosted on VPS). Attacker added few php scripts that were redirecting to some ad sites. We have cleaned everything (or at least we think we did), and now everything works as it should.
However, links on Google (or Yahoo) that are pointing to our web site are still trying to include these php scripts (and returns 404 as these are deleted now). Direct links from browser works as they should.
We have cleaned site 10 days ago, so I do not think that something is cached at Google servers. Re-indexing should be done by now.
To reproduce this behavior:
Go to www.google.com
type in "anitex socks"
click any php link that starts with "anitexsocks.com"
You will get "The requested URL /wp-includes/client.php was not found on this server" + 404 error
Refresh page and everything works without issues
Why are only Google links making troubles?
Any help is welcome. Thanks!
As for the reason why this is happening, I installed a firefox add-on which blocks my browser's Referrer Header and then followed a Google link to your site and it worked fine. Then I disabled the add-on and the problem started occurring again.
This shows that there is still some malicious code running on your website which is checking all http requests to see if they come from Google (based on checking the HTTP Referrer header) and redirecting them to /wp-includes/client.php if they do,
To try to determine where this code may lie, try performing a recursive grep through all your www files on your server as well as your www configuration files,somewhere in there there must still be a reference to that client.php script, hopefully you can find and eliminate it.
That said, if it were my site and I knew a hacker had had free reign over my server to do whatever they wanted to it, I would not mess around with trying to undo the damage and would instead restore the most recent backup from before the site was hacked. You only have to miss one back door the hacker left in place and they can re-enter your site. After restoring backups, you should also upgrade/reconfigure the software they used to gain access in the first place so they can't simply rehack it in the same manner again.
So I have a site setup on a server. It has been working for ever. All of a sudden it stops working. I tried going to it even by IP. It just says, "Under Construction..
Under Construction
The site you are trying to view does not currently have a default page. It may be in the process of being upgraded and configured..."
I check to make sure it was pointing at the right virtual dir and that the default page was set in the documents list. The default page does exist in the dir too....
Nothing has been changed via code. Nothing has been altered on the server. I have a bunch of other sites running on the same server and they are all coming up. Just wondering if there was something that may have happened or overlooked. Any thoughts or ideas?
Thanks a million.
Double check your bindings are set correctly. Perhaps a new site was created which conflicts with the bindings of your site?
Edit
Make sure .net is set to the right version. I've seen where pages are not served up when the web is set to 1.1 on a 2.0 site.
Also does the site work locally on the box? Have you ruled out firewall issues / changes or other network related elements.
It sounds like your request is being handled by another IIS site. Make sure that the host header is set correctly.
With your comment, the "Bad Request" error means that the default web site was handling the request. There are a couple of things you can check:
If this is not the site that you expected to serve your app, then you still have a website identity issue.
If your app is hosted on the default web site, then make sure that the default document is set correctly.
Also make sure that you don't have a file named "app_offline.htm" in your app's root.
Well we rebooted the server and now it works again. I guess I should have tried that in the first place. It was just odd that all the otehr sites were working. Anyway thanks for suggestions everyone.
A cheeseburger to the first person who can help me make sense of this. I have a page in a Sharepoint app that uses Telerik's RadUpload to upload files. This has worked for months; last week it stopped working (in Internet Explorer, this detail is important). After talking with a co-worker about the problem, I tried the upload with Firefox; it worked. Not only that, all subsequent uploads from Internet Explorer started working. Flash forward an hour, and the aforementioned coworker, on another Sharepoint site, running on different servers, was having problems downloading (using Internet Explorer). Being half serious, half smart-aleck, I said 'try it in Firefox'. Not only did that work, ALL SUBSEQUENT DOWNLOADS IN INTERNET EXPLORER WORKED! And he re-produced this behavior on another machine. My fear is that this a browser issue. All advice will be greatly appreciated.
a
IE will try and present credentials to a server it knows to be in its Local Intranet zone when it tries to connect (depending on the setting of "Automatic logon only in Intranet zone").
Firefox will only present credentials when prompted, and will generally ask you by popping up a box (unless you've configured a list of sites for it to always present NTLM credentials to).
I've seen a similar case with Sharepoint where you can cause IE to work by logging in with Firefox. I theorized it was due to a permission on a remote resource being for "Authenticated Users", and you're causing your user to authenticate by logging in forcefully. We eventually set the "Automatic logon only in Intranet zone" to "Prompt" and it worked. My theory there was that it wasn't detecting the site as being in the Local Intranet zone for some reason. If you're not accessing a domain with no .'s in it, try also setting your Local Intranet site policy to match the full domain of the Sharepoint server, not just *.example.com - I've read that that can help.
Was it as simple as IE not re-downloading miss-cached .js file, maybe, that firefox did download, making IE work after that?
Pretty gnarly to debug.