jefffernando
New Pleskian
Hello to the whole community, I am new.
Plesk Obsidian 18.0.28.
I will try to communicate in the best possible way, my native speaking is Spanish, if something is not clear please let me know.
Currently I bought a web hosting, where it allows Unlimited Dedicated app pools.
The problem I am having is that the session of my user in your application closes every 5 minutes, and that is very little time.
I configured the section where it says windows authentication in 60 minutes and in my application too, I think this happens because the session is hosted in IIS POOL and due to inactivity it is recycled every 5 minutes (configured by default in shared windows hosting, no I can change it)
View attachment 17369
Cookies are kept in my application's browser, but the session is lost, it requests to log in again, this is because when the application is hosted in the APP pool, it restarts and being in the volatile memory, the session is lost .
View attachment 17370
Try to publish the dotnet core application out of process (you shouldn't miss the session, you still get lost)
Search a lot of information on the web and I can't solve my problem, if someone had this problem, or some similar experience it would be very helpful.
Best regards,
Plesk Obsidian 18.0.28.
I will try to communicate in the best possible way, my native speaking is Spanish, if something is not clear please let me know.
Currently I bought a web hosting, where it allows Unlimited Dedicated app pools.
The problem I am having is that the session of my user in your application closes every 5 minutes, and that is very little time.
I configured the section where it says windows authentication in 60 minutes and in my application too, I think this happens because the session is hosted in IIS POOL and due to inactivity it is recycled every 5 minutes (configured by default in shared windows hosting, no I can change it)
View attachment 17369
Cookies are kept in my application's browser, but the session is lost, it requests to log in again, this is because when the application is hosted in the APP pool, it restarts and being in the volatile memory, the session is lost .
View attachment 17370
Try to publish the dotnet core application out of process (you shouldn't miss the session, you still get lost)
Search a lot of information on the web and I can't solve my problem, if someone had this problem, or some similar experience it would be very helpful.
Best regards,