# Troubleshooting > Solve problems with TX Text Control .NET Server: packages and licenses, the Document Editor connection, Linux, Docker, IIS, Azure, fonts and conversions. - **Product:** TX Text Control .NET Server - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET Server > Troubleshooting - **1047 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/llms-full.txt --- Something doesn't work: a package isn't found, the Document Editor stays empty, a document has the wrong fonts or the application ends when it starts. What you see usually tells you where to look, and each page of Troubleshooting starts from such a symptom, quotes the message where TX Text Control shows one, explains the cause and gives the steps that fix it. ### Find the Right Page | If you see | Read | |---|---| | A TX Text Control package isn't found, doesn't install or has the wrong version | [Installation](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/installation/llms-full.txt) | | The private NuGet feed rejects your credentials or doesn't list a package | [NuGet Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/nuget-authentication/llms-full.txt) | | Trial text in documents, or an exception with a license message | [Licensing](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/licensing/llms-full.txt) | | The editor has no height, reports that it's already initialized, or your code runs too early | [Document Editor](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/document-editor/llms-full.txt) | | "Can't connect to the server." in the editor, or a lost connection | [WebSockets](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/websockets/llms-full.txt) | | An application that works on Windows fails on a Linux server | [Linux](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/linux/llms-full.txt) | | A container stops, doesn't restore its packages or can't reach the backend | [Docker](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/docker/llms-full.txt) | | Text in another font, or moved line and page breaks | [Fonts](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/fonts/llms-full.txt) | | Error 500.30 on IIS, or editors that lose their sessions after a while | [IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/iis/llms-full.txt) | | An application that doesn't start or connect on Azure App Service | [Azure](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/azure/llms-full.txt) | | A `FilterException`, or a converted document that looks wrong | [Document Conversion](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/conversion/llms-full.txt) | | The application fails when the engine starts, or `Create` returns `false` | [Native Library / Runtime Errors](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/native-libraries/llms-full.txt) | ### Collect the Evidence First Most problems are quicker to solve with the right output at hand: - **The browser console.** The Document Editor logs the address it connects to and most connection errors there. See [Find Out Where the Connection Fails](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/websockets/#find-out-where-the-connection-fails). - **The log of your application.** The messages of the Document Editor backend appear in it with the prefix `[TXTextControl.Web.Server.Core]`. On IIS, turn on the log of the ASP.NET Core Module first, as [Read the Log of the Application](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/iis/#read-the-log-of-the-application) describes. - **The reason of an exception.** A `FilterException` names its cause in its `Reason` property and an error number in its message. See [Read the Reason of a FilterException](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/conversion/#read-the-reason-of-a-filterexception). - **The replaced fonts.** The `AdaptFont` event reports every font that isn't available. See [Find Out Which Fonts Are Replaced](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/fonts/#find-out-which-fonts-are-replaced). - **The installed version.** Which product level and service pack an application runs with shows [Check Which Version Your Application Runs](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/licensing/#check-which-version-your-application-runs). ### Where to Start 1. **A new setup doesn't work:** start with [Installation](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/installation/llms-full.txt) and [Licensing](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/licensing/llms-full.txt), then the page of the environment you deploy to: [Linux](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/linux/llms-full.txt), [Docker](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/docker/llms-full.txt), [IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/iis/llms-full.txt) or [Azure](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/azure/llms-full.txt). 2. **The Document Editor doesn't show up:** [WebSockets](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/websockets/llms-full.txt) first, because most editor problems are connection problems, then [Document Editor](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/document-editor/llms-full.txt). 3. **Documents look wrong:** [Fonts](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/fonts/llms-full.txt) first, then [Document Conversion](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/conversion/llms-full.txt). If a problem started after an update, check the [Breaking Changes](https://docs.textcontrol.com/tx-text-control-dotnet-server/whats-new/breaking-changes/llms-full.txt) of the versions you skipped. The [Deployment Guide](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/llms-full.txt) shows complete setups that avoid many of these problems. --- ## In This Section - [Azure](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/azure/llms-full.txt): Fix problems on Azure App Service: Web sockets off, 32-bit platform, target runtime, the Windows sandbox, the Free tier, session affinity and fonts on Linux. - [Document Conversion](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/conversion/llms-full.txt): Solve conversion errors with ServerTextControl: FilterException reasons, wrong StreamType, protected PDFs, PDFs without text, missing images and DOC on Core. - [Docker](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/docker/llms-full.txt): Fix container problems: base images and gconv, fonts in the image, restoring from the private feed in docker build, ports and a backend in another container. - [Document Editor](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/document-editor/llms-full.txt): Fix Document Editor errors in ASP.NET Core, Angular, React and Blazor: no height, TXTextControl.init errors, an editor already initialized and early API calls. - [Fonts](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/fonts/llms-full.txt): Fix font problems: replaced fonts, the Fonts folder of the Core engine, a failed font installation, AdaptFont, fonts in PDF/A, the editor and the viewer. - [IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/iis/llms-full.txt): Fix IIS problems with TX Text Control .NET Server: error 500.30, 32-bit pools, the WebSocket Protocol, idle time-outs, recycling, sub-applications and fonts. - [Installation](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/installation/llms-full.txt): Fix installation errors of TX Text Control .NET Server: SDK packages not found, missing sources, target frameworks, mixed versions, NETSDK1082, ERESOLVE. - [Licensing](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/licensing/llms-full.txt): Fix license problems of TX Text Control .NET Server: trial text in documents, an expired trial, controls that could not be licensed and LicenseLevelException. - [Linux](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/linux/llms-full.txt): Fix Linux problems: the Classic package, glibc and gconv modules, ICU, the dotnet command, the working directory, permissions and case-sensitive file names. - [Native Library / Runtime Errors](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/native-libraries/llms-full.txt): Fix startup errors of TX Text Control .NET Server: 32-bit processes, ARM64 and Alpine, Classic outside Windows, missing runtimes and Create returning false. - [NuGet Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/nuget-authentication/llms-full.txt): Solve problems with the Text Control Private NuGet Feed: 401 responses, expired API tokens, missing packages, an ignored nuget.config and build servers. - [WebSockets](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/websockets/llms-full.txt): Fix Document Editor connection problems: pipeline order, the middleware, the backend port 4283, rejected handshakes, proxies, WebSocket URLs and reconnection. --- ## Nearby - **Previous:** [Performance Best Practices](https://docs.textcontrol.com/tx-text-control-dotnet-server/performance/best-practices/llms-full.txt) - **Next:** [Installation](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/installation/llms-full.txt)