Typo3 CMS keeps kicking me out - azure-web-app-service

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

Related

Drupal site moved, now accounts cannot be opened

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

Google links opens wrong pages

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.

Azure based Umbraco site - when logging in, I get logged back out immediately

I have recently installed a website project on Azure and that was relatively easy to do thanks to great docs online. We are having a problem with the back office (admin) login though, it's a bit strange, as it didn't happen straight away, I shall elaborate....
When I go to http://www.keelycattschoolofdance.co.uk/umbraco/ it takes me to the login page, which seems fine.
(The url at this point becomes www.keelycattschoolofdance.co.uk/.../login.aspx)
I then login, which works and it starts to display the admin panels but then bounces back to the login and the URL becomes www.keelycattschoolofdance.co.uk/.../login.aspx
I am running this on Azure using the Accelerator, latest version of Umbraco and using SQL CE 4.0 rather than SQL Server.
has anyone seen this before?
Please let me know if you need more information, I shall respond :-)
Thanks in advance
Nick
It sounds like it may be a Session error. This is a problem for Azure and Umbraco because Azure uses round robin load balancing.
The normal way of setting up an Umbraco site using the accelerator would be to have a separate session DB where the shared session state is stored.
Make sure you are using this accelerator for Umbraco on Azure as it's the latest and best.
http://waacceleratorumbraco.codeplex.com/
We have several large production sites using this and I can confirm they all work fine (including the backend editing environment).
Things to watch out for are that you need to follow the instructions closely as they are easy to get wrong :-)
Make sure you don't have dashes in your db names as this makes things go wrong as well.
Finally if you are using more than one web role the Umbraco preview can sometimes yellow screen, as the preview XML may not be on the server that gets to the preview request. This is again because of the round robin load balancing.

logging urls in IIS

A little over a year ago we started getting hit with sql injection attacks. We have hundreds of sites so we ended up spending weeks patching any holes we could find. Then a few weeks ago we started getting hit again. We've gone through everything we can think of and we can't find anywhere where the person is getting in. Does anyone know if there's a way to write a script for IIS that will allow me to record every url or posted data that IIS encounters? And because we've got so many sites I'm looking to set up something that doesn't have to be set up for each individual site but that I can set up at the root of the IIS tree. Thanks.
You don't need a script for URL data it can logged in the regular IIS logs.
See this article about setting up the logs.
The first place too look is the Log files (Assuming you are using IIS 6.0, see here for a tutorial how to find them)
The IIS log does not store posted Data though. Look here for a discussion regarding logging post data.
As mentioned above, IIS logs all requests to a web site, unless you have unchecked "Enable Logging". You might want to look in to UrlScan 3.0, which also handles possible SQL injection scenarios, see the section entitled "Rule to Block SQL injection Signatures"

Sharepoint Services 3.0 CSS not working

Sometimes the style sheet disappears when naviguating on our WSS 3.0 sites (white background on the site, no colors, no formatting, etc.). This has mainly happened with IE6 (corporate browser for the majority of our computers). The fixes were :
clean up temporary internet files
if it still doesn't work, upgrade to IE 7
However, this time, the upgrade to IE 7 hasn't worked, the style sheet isn't applied. When we clean up temporary internet files, things go back to normal, but after a while the css disappears again.
Here are a few ideas on what you could try:
Fiddler should be able to tell you if there is a network problem.
Check the HTML for anything unusual. Is it malformed in any way? Can you save a copy and run it through an online validator (although this is limited in use as SharePoint's default markup isn't compliant).
If some users are having the issues but others aren't, check their permissions on the server.
You could also try using the SharePoint "Log in as another user" feature to see if the problem can be reproduced on your machine when logged in as them. You may also want to try running Internet Explorer as that user.
Check the Event Viewer on both client and server for anything unusual.
Check the IIS logs on the server for any errors.
Check the SharePoint ULS logs on the server in the "12 Hive" for errors that might be related to this problem.
Try running Process Monitor on the client and reproduce the problem. Search for keywords such as FAIL or ERROR to see if anything appears. Make a note of the time the problem occurs and see if the Process Monitor logs give any additional information.
Is there some javascript that's involved as well? Could it be a virus scanner that is set way to strict? As you pointed out in one of the comments, the CSS isn't even being requested (at IIS log level, which is as basic as you get, not even in SHarePoint yet), so it HAS to be something on the client PC.

Resources