session is working in local is not working in public url?

Hi Velladurai,

It could be due to several reasons related to configuration, hosting environment, or permissions.

Check Web.config for Session Configuration: Ensure that your session state configuration in Web.config is correct and consistent with the session state mode you intend to use (e.g., InProc, StateServer, SQLServer).
```
    
```
Session Timeout: Verify the session timeout settings in Web.config and ensure it is not too short.
Check Machine Key: If your application is hosted in a web farm or load-balanced environment, ensure that the machine key is specified in Web.config to avoid issues with session data.
```
  
```
Permissions: Ensure that the application pool identity has the necessary permissions to write to the session state store (if using StateServer or SQLServer modes).
Firewall/Network Configuration: Ensure that firewalls or network configurations are not blocking session state communication if using StateServer or SQLServer modes.
Browser Cookies: Ensure that the browser accepts cookies, as session state relies on cookies by default. Check if there are any cookie-related issues or restrictions.
Host Configuration: If hosted on a third-party service, check their documentation for any specific configurations or restrictions related to session state management.
Check for Exceptions: Look at the application's logs to see if there are any exceptions or errors related to session state.
Custom Session State Provider: If using a custom session state provider, ensure it is correctly configured and functional.
Session ID Change: Check if the session ID is changing unexpectedly. This can be caused by issues like mualtiple cookies being sent with the request.

Example Web.config for SQL Server Session State

If you decide to use SQL Server for session state, here is an example configuration:

Ensure that the SessionStateDB database is created and properly configured on your SQL Server.

Debugging Steps

Local vs. Public URL:
- Compare the configuration settings between your local and public deployments.
- Ensure that there are no environment-specific settings that differ and affect session state.
Inspect Network Traffic: Use browser developer tools to inspect network traffic and check for any issues with session cookies being sent or received.
Log Session State Data: Add logging to track session state data to ensure it is being set and retrieved correctly.

By following these steps, you should be able to identify and resolve issues related to session state not working on a public URL in an ASP.NET MVC application. If you still encounter issues, please provide more details about your specific configuration and environment.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Aman Gupta2y ago
Hi Velladurai,

It could be due to several reasons related to configuration, hosting environment, or permissions.
1. Check Web.config for Session Configuration: Ensure that your session state configuration in Web.config is correct and consistent with the session state mode you intend to use (e.g., InProc, StateServer, SQLServer).
2. Session Timeout: Verify the session timeout settings in Web.config and ensure it is not too short.
3. Check Machine Key: If your application is hosted in a web farm or load-balanced environment, ensure that the machine key is specified in Web.config to avoid issues with session data.
4. Permissions: Ensure that the application pool identity has the necessary permissions to write to the session state store (if using StateServer or SQLServer modes).
5. Firewall/Network Configuration: Ensure that firewalls or network configurations are not blocking session state communication if using StateServer or SQLServer modes.
6. Browser Cookies: Ensure that the browser accepts cookies, as session state relies on cookies by default. Check if there are any cookie-related issues or restrictions.
7. Host Configuration: If hosted on a third-party service, check their documentation for any specific configurations or restrictions related to session state management.
8. Check for Exceptions: Look at the application's logs to see if there are any exceptions or errors related to session state.
9. Custom Session State Provider: If using a custom session state provider, ensure it is correctly configured and functional.
10. Session ID Change: Check if the session ID is changing unexpectedly. This can be caused by issues like mualtiple cookies being sent with the request.
Example Web.config for SQL Server Session State

If you decide to use SQL Server for session state, here is an example configuration:
```
    
```
Ensure that the SessionStateDB database is created and properly configured on your SQL Server.

Debugging Steps
1. Local vs. Public URL:
  
  Compare the configuration settings between your local and public deployments.
  
  Ensure that there are no environment-specific settings that differ and affect session state.
2. Inspect Network Traffic: Use browser developer tools to inspect network traffic and check for any issues with session cookies being sent or received.
3. Log Session State Data: Add logging to track session state data to ensure it is being set and retrieved correctly.
By following these steps, you should be able to identify and resolve issues related to session state not working on a public URL in an ASP.NET MVC application. If you still encounter issues, please provide more details about your specific configuration and environment.