We have suffered from this issue before when setting up a new project on Azure. Old thread: https://discord.com/channels/869656431308189746/1183873525031911554 Now, we are seeing this issue on local development on localhost:8080 on a project where we're upgrading from Umbraco 10 to 13. After logging into the CMS, there is about a 40-60 second wait. Then there is a call to

/umbraco/backoffice/umbracoapi/authentication/GetRemainingTimeoutSeconds

that returns:

)]}',
0.0

Upon which the user is logged out showing message "Session timed out." We have tried using incognito mode to rule out cookies, as well as completely fresh browser profile in Chrome. Are we missing something completely basic for this problem to occur? appsetting Umbraco.CMS.Global.TimeOut is set to

08:00:00

. 8 hours is more than 1 minute. We have not supplied any other setting that should affect this. In our previous 'fresh' project the settings were also default. Umbraco.CMS.Security.KeepUserLoggedIn is not set to

true

thus it should be interpreted as the default

false

. > When set to false a user will be logged out after a specific amount of time has passed with no activity. You can specify this time span in the global settings with the TimeOut key. This is exactly what we've done. Umbraco.CMS.Security.AllowConcurrentLogins is showing a bit of a strange behavior. We don't have this defined at all. But setting it to true, and then restarting Umbraco, and then simply reloading the browser window of the recently auto-logged out user in a fresh browser profile will automatically log them in and show the backoffice. Logging out above mentioned user and then logging in seems to work fine as well.

GetRemainingTimeoutSeconds

returns the full 8 hours. However, logging out, setting

AllowConcurrentLogins

to false again and then logging back in, the problem reappears. In our tests, this is the only browser window using the site. Why are we seeing this problem?

I'm getting the following error when starting up my Umbraco site, does anyone have any pointers in where to look?

System.InvalidOperationException: No data for media 1120
   at Umbraco.Cms.Infrastructure.PublishedCache.Persistence.NuCacheContentRepository.CreateMediaNodeKit(ContentSourceDto dto, IContentCacheDataSerializer serializer)
   at Umbraco.Cms.Infrastructure.PublishedCache.Persistence.NuCacheContentRepository.GetAllMediaSources()+MoveNext()
   at Umbraco.Extensions.EnumerableExtensions.InGroupsOf[T](IEnumerable`1 source, Int32 groupSize)+MoveNext()
   at Umbraco.Cms.Infrastructure.PublishedCache.ContentStore.SetAllFastSortedLocked(IEnumerable`1 kits, Int32 kitGroupSize, Boolean fromDb)

What are the recommended minimum requirements for hosting Umbraco (13+) on-prem? I can only seem to find that the minimum recommended Azure tier is S2 but nothing about on prem. What would the equivalent for a server be?

Hello everyone, I am encountering some challenges with handling Save and Publish events in Umbraco, specifically using SaveAndPublishHandler class. Here are the details of my issue: **Problem Description**: I have implemented a SaveAndPublishHandler class in Umbraco to handle Saved and Published events for content items. The goal is to send an HTTP POST request to an external endpoint whenever content is saved or published with a specific ParentId (in my case, ParentId 1249). *Code : *

c#
        public SaveAndPublishHandler(IContentService contentService)
        {
            _contentService = contentService;
        }

        public void Initialize()
        {
            ContentService.Saved += ContentService_Saved;
        }

        public void Terminate()
        {
            ContentService.Saved -= ContentService_Saved;
        }

        private void ContentService_Saved(IContentService sender, SaveEventArgs<IContent> e)
        {
            foreach (var content in e.SavedEntities)
            {
                if (content.ParentId == 1249)
                {
                    var dataToSend = new { ContentId = content.Id, Title = content.Name };
                    var json = Newtonsoft.Json.JsonConvert.SerializeObject(dataToSend);
                    var contentToSend = new StringContent(json, Encoding.UTF8, "application/json");

                    using (var httpClient = new HttpClient())
                    {
                        var endpointUrl = "http://localhost:65137/umbraco/surface/UpdateApprovedAccount/UpdateApprovedAccountV2"; 

                        var response = httpClient.PostAsync(endpointUrl, contentToSend).Result;

                        var responseContent = response.Content.ReadAsStringAsync().Result;
                    }
                }
            }
        }

Composing :

c#
public void Compose(Composition composition) {
composition.Components().Append<SaveAndPublishHandler>();
}

Hi there 👋, I'm trying to host my Umbraco 13 CMS on my debian server. I installed .net8.0, umbraco (along with its templates), created a .service file so the CMS can run as a service and ran

dotnet publish --os linux

. Before running the service i started the web with dotnet build and synchornized some files so it installation would match my lcoal dev. That said, with

dotnet build

Umbraco worked perfectly fine - frontend, backend, file handling all went well. But with the service running the backend doesn't seem to work anymore. The browser is trying to fetch files like https://mydomain.com/umbraco/login/login.iife.js but the kestrel server just returns a 404. Nothing obvious is logged. I didn't find anything similiar yet - has anyone an idea what might be the cause / solution to the cause? This is my .service file:

[Unit]
Description=Noels umbraco CMS web
Wants=network.target
After=network.target

[Service]
WorkingDirectory=/var/www/html/myWebProject/
ExecStart=/usr/bin/dotnet /var/www/html/myWebProject/bin/Release/net8.0/linux-x64/publish/myWebProject.dll
SyslogIdentifier=NCSumbraco
User=root
Restart=always
RestartSec=5
KillSignal=SIGINT
Environment=ASPNETCORE_ENVIRONMENT=Production
Environment=DOTNET_PRINT_TELEMETRY_MESSAGE=false
Environment=ASPNETCORE_URLS=https://*:44332

[Install]
WantedBy=multi-user.target

Thanks!

We've got Umbraco hosted in Azure, in a load-balanced environment with deployment slots. We're seeing a lot of warnings in the logs. Umbraco Version 13.0.1 W : Error unprotecting the session cookie. Stack Trace : System.Security.Cryptography.CryptographicException: The key {078a31d2-3d8c-4b43-baeb-a639524b05c5} was not found in the key ring. For more information go to https://aka.ms/aspnet/dataprotectionwarning at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.UnprotectCore(Byte[] protectedData, Boolean allowOperationsOnRevokedKeys, UnprotectStatus& status) at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Unprotect(Byte[] protectedData) at Microsoft.AspNetCore.Session.CookieProtection.Unprotect(IDataProtector protector, String protectedText, ILogger logger) We also see a rare instance of an error, but this seems much less frequent Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The antiforgery token could not be decrypted. Stacktrace : System.Security.Cryptography.CryptographicException: The key {84cea658-5bcd-439a-b175-d1c4bb7956f7} was not found in the key ring. For more information go to https://aka.ms/aspnet/dataprotectionwarning at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.UnprotectCore(Byte[] protectedData, Boolean allowOperationsOnRevokedKeys, UnprotectStatus& status) at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Unprotect(Byte[] protectedData) at Microsoft.AspNetCore.Antiforgery.DefaultAntiforgeryTokenSerializer.Deserialize(String serializedToken) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Antiforgery.DefaultAntiforgeryTokenSerializer.Deserialize(String serializedToken) at Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery.GetCookieTokenDoesNotThrow(HttpContext httpContext) Anyone seen this issue, or similar?

I am on my way to create some custom database tables i have follow this pice og documentation https://docs.umbraco.com/umbraco-cms/tutorials/getting-started-with-entity-framework-core But when i try the CLI command "dotnet ef migrations add AddResevertionTables --context ..." I get an error: Unable to create a 'DbContext' of type ''. The exception 'Unable to resolve service for type 'Microsoft.EntityFrameworkCore.DbContextOptions`1[Project.WebSite.Infrastructure.DbContexts.ProjectDbContext]' while attempting to activate 'Project.WebSite.Infrastructure.DbContexts.ProjectDbContext'.' was thrown while attempting to create an instance. For the different patterns supported at design time, see https://go.microsoft.com/fwlink/?linkid=851728 But have no clue why this happign and can not move on can somebody help me

I'm a Tailwind newbie and although it's still feels a bit "wrong" I'm persevering with it. One issue I've come across is what to do in an RTE stylesheet. Is there some trick to getting the TW classes to output to the front end while still showing the manual styles in the editor itself? Thanks.

In a class using IUmbracoContextFactory, I'm trying to get the Guid of a node for later use, but all I get is a load of 00000's. I've tried many things but none work. I think this should work but it doesn't:

var orderConfirmedGuid = siteRoot.DescendantsOrSelf<GeneralPage>().Where(x => x.Name == "Order Confirmed").FirstOrDefault().GetUdi().AsGuid();

I can get the Id, so I know the Name string is correct, but not the Guid. Any ideas? Thanks.

From v13 methods such as umbracohelpers

ContentSingleAtXPath

is being deprecated. For example, we get our global settings node as such:

var globalSettings = (GlobalSettings)_umbracoHelper.ContentSingleAtXPath("//globalsettings");

How can we get the same published content but adhering to current conventions? Looking at the documentation there is a method

Content

that takes a

guid

, but we do not wish to rely on a hard coded guid for this scenario. We need to base this on what the slug is named within the backoffice. And yes, we know there might be other approaches that do not rely on the slug to solve this, but this is our current scenario and not the only instance we need to cater to.