<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://serverappmanager.ommrudraksha.com/blog/</id>
    <title>Server App Manager journal</title>
    <updated>2026-11-21T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://serverappmanager.ommrudraksha.com/blog/"/>
    <subtitle>Server App Manager Blog</subtitle>
    <icon>https://serverappmanager.ommrudraksha.com/img/server-mark.svg</icon>
    <rights>Copyright 2026 OmmLabs</rights>
    <entry>
        <title type="html"><![CDATA[Find ASP.NET Core services running under systemd]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Review existing .NET service candidates, confirm the unit and listening port, and register only the applications you manage.]]></summary>
        <content type="html"><![CDATA[<p>Finding an application on a Linux server means identifying the service that owns its process, not guessing from a domain name. On a shared Ubuntu machine, deployment folders, service units and public websites can all use different names.</p>
<p>Server App Manager includes a discovery step for recognizable .NET services. This guide explains how to review its results, what the current scan can miss, and when manual verification is necessary. All service names and addresses below are examples for an isolated lab.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="begin-with-the-application-owner">Begin with the application owner<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#begin-with-the-application-owner" class="hash-link" aria-label="Direct link to Begin with the application owner" title="Direct link to Begin with the application owner" translate="no">​</a></h2>
<p>Before scanning, decide which applications you are responsible for. A list of services is not a grant of permission to manage every item in it.</p>
<p>Ask the owner for the expected application, environment and service identity where those are known. Record whether it is a public website, an internal HTTP application or a background worker. That context helps you interpret a missing website URL or listening port.</p>
<p>For a lab, use a unit such as <code>demo-web.service</code> and a separate worker unit. Keep the expected mapping in a short note. The exercise succeeds when the discovered information agrees with that mapping, not merely when the scan returns a long list.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="know-what-the-current-discovery-recognizes">Know what the current discovery recognizes<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#know-what-the-current-discovery-recognizes" class="hash-link" aria-label="Direct link to Know what the current discovery recognizes" title="Direct link to Know what the current discovery recognizes" translate="no">​</a></h2>
<p>The source preview scans loaded systemd service information for recognizable .NET launch patterns. It can identify a direct <code>dotnet</code> launch and an executable with a neighboring runtime configuration file.</p>
<p>These patterns are useful clues rather than a complete application inventory. A shell wrapper, custom launcher, unusual deployment layout or inaccessible file can prevent recognition. A service may also exist on disk without appearing as the kind of loaded unit the scan considers.</p>
<p>The <a href="https://github.com/OmmLabs/MyServerManager/blob/main/README.md" target="_blank" rel="noopener noreferrer" class="">application README</a> describes current recognition behavior. Check that behavior against the revision you are evaluating instead of assuming every future .NET hosting model is covered.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="keep-the-names-separate">Keep the names separate<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#keep-the-names-separate" class="hash-link" aria-label="Direct link to Keep the names separate" title="Direct link to Keep the names separate" translate="no">​</a></h2>
<p>A friendly display name is for people. The systemd unit name identifies the management target. A deployment directory locates files. The assembly name identifies an application artifact. None of these fields automatically determines the public hostname.</p>
<p>For example, a lab registry entry might have the display name “Demo website — test” and the unit <code>demo-web.service</code>. Its public address could be <code>https://web.example.com</code>, while the process listens on a local application port.</p>
<p>Do not normalize these fields by making them all resemble the website name. Preserve the real unit identity and use the friendly display name to make the list easier to read.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="open-find-apps-and-inspect-a-candidate">Open Find apps and inspect a candidate<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#open-find-apps-and-inspect-a-candidate" class="hash-link" aria-label="Direct link to Open Find apps and inspect a candidate" title="Direct link to Open Find apps and inspect a candidate" translate="no">​</a></h2>
<p>Sign in to the local dashboard with your verified SSH registration. Open <strong>Applications</strong> and choose <strong>Find apps</strong>.</p>
<p>Look at a candidate's service name and any available path, assembly and port information. Decide whether it corresponds to an application you intend to manage. If two entries have similar names, compare their environment and deployment details before opening the registration form.</p>
<p>Choose <strong>Review and add</strong> for one candidate. The review step is intentional: it gives you a chance to correct a display name, add a known public URL and reject an unrelated unit. Discovery does not silently enroll every result.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="verify-the-canonical-unit">Verify the canonical unit<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#verify-the-canonical-unit" class="hash-link" aria-label="Direct link to Verify the canonical unit" title="Direct link to Verify the canonical unit" translate="no">​</a></h2>
<p>A canonical unit name is the identity systemd reports for the loaded service. The dashboard validates the service before saving a registration and before management operations.</p>
<p>If you need independent inspection in an authorized lab, a read-only command can request the relevant identity and state:</p>
<div class="language-sh codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#bfc7d5;--prism-background-color:#292d3e"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-sh codeBlock_bY9V thin-scrollbar" style="color:#bfc7d5;background-color:#292d3e"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#bfc7d5"><span class="token plain">systemctl show demo-web.service -p Id -p LoadState -p ActiveState -p MainPID</span><br></div></code></pre></div></div>
<p>The displayed values are evidence to compare, not sample values to copy into the registry. A missing unit, an alias and a loaded canonical service are different cases. The <a href="https://www.freedesktop.org/software/systemd/man/latest/systemctl.html" target="_blank" rel="noopener noreferrer" class="">systemctl manual</a> documents inspection commands and the distinction between loaded units and installed unit files.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="treat-detected-ports-as-observations">Treat detected ports as observations<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#treat-detected-ports-as-observations" class="hash-link" aria-label="Direct link to Treat detected ports as observations" title="Direct link to Treat detected ports as observations" translate="no">​</a></h2>
<p>A listening port is a point-in-time observation of a socket visible to the account. It may not be available when a service is stopped or starting. Some services open several sockets; a worker may open none.</p>
<p>A port detected during discovery should therefore be checked against the intended application. If it is missing, investigate before filling it with a number remembered from another deployment.</p>
<p>A registry port is useful operational metadata, but it does not edit Kestrel or the proxy configuration. Changing that field alone cannot move an existing service to another listener. Keep the dashboard's metadata aligned with verified server configuration.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="add-the-website-url-deliberately">Add the website URL deliberately<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#add-the-website-url-deliberately" class="hash-link" aria-label="Direct link to Add the website URL deliberately" title="Direct link to Add the website URL deliberately" translate="no">​</a></h2>
<p>For a public website, enter its actual HTTP or HTTPS URL. The dashboard's health checker uses that address from your PC.</p>
<p>An internal listener and the public site can differ because Nginx handles the public connection. Likewise, several public routes can reach a shared application. A valid local port does not prove that a particular public URL maps to that unit.</p>
<p>Leave unrelated website assumptions out of worker registrations. If your application has no appropriate public endpoint, understand that limitation rather than adding a random homepage to obtain a green health indication.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="save-one-application-and-inspect-its-state">Save one application and inspect its state<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#save-one-application-and-inspect-its-state" class="hash-link" aria-label="Direct link to Save one application and inspect its state" title="Direct link to Save one application and inspect its state" translate="no">​</a></h2>
<p>After reviewing the fields, save the registration and return to Applications. Open its status and recent logs before using a management button.</p>
<p>Confirm that the displayed unit remains the one you reviewed. Check the main PID and available service memory. If the process is stopped, those readings can be unavailable; a missing current PID is not a reason to fabricate a value.</p>
<p>Look at the last-check time and refresh after a known state change. The dashboard caches status information between sampling intervals, so it represents a recent observation rather than a continuous stream of every process transition.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-manual-registration-for-a-verified-exception">Use manual registration for a verified exception<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#use-manual-registration-for-a-verified-exception" class="hash-link" aria-label="Direct link to Use manual registration for a verified exception" title="Direct link to Use manual registration for a verified exception" translate="no">​</a></h2>
<p>A wrapper-based application can still be manageable even when automatic discovery cannot recognize its .NET runtime. Verify its canonical systemd unit with the server owner, then use the manual registration facility.</p>
<p>Keep deployment metadata factual. If the assembly name does not apply to a native app host, do not invent one for consistency. The management boundary is the validated service unit, while supplementary fields help an operator understand what it represents.</p>
<p>A useful discovery bug report describes the launch pattern with private paths and arguments removed. Full launch commands can contain configuration details, so share only what is necessary to reproduce the recognition problem.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="organize-the-list-for-everyday-use">Organize the list for everyday use<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#organize-the-list-for-everyday-use" class="hash-link" aria-label="Direct link to Organize the list for everyday use" title="Direct link to Organize the list for everyday use" translate="no">​</a></h2>
<p>Use distinct environment labels and display names when applications share a business name. Put frequently used services near the top through display order.</p>
<p>An enabled setting and removal serve different purposes. Disabling retains the entry for later use. Removing unregisters it from the local dashboard and records the change; it does not uninstall the application.</p>
<p>If another operator maintains a registry on another PC, remember that these are local registrations. A rename in your list is not a server-side rename, and removing an entry from your dashboard does not remove the corresponding entry from someone else's local state.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="check-a-framework-dependent-and-an-executable-deployment">Check a framework-dependent and an executable deployment<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#check-a-framework-dependent-and-an-executable-deployment" class="hash-link" aria-label="Direct link to Check a framework-dependent and an executable deployment" title="Direct link to Check a framework-dependent and an executable deployment" translate="no">​</a></h2>
<p>For a reproducible lab review, compare two existing sample services: one that starts with <code>dotnet</code> and one that launches an app executable beside its runtime configuration file.</p>
<p>Record what the scan recognized, whether the service was loaded, which listening port was visible, and what you verified manually. Do not assume both services should expose an HTTP endpoint.</p>
<p>The <a href="https://learn.microsoft.com/en-us/dotnet/core/deploying/" target="_blank" rel="noopener noreferrer" class="">.NET deployment guide</a> describes deployment forms, while the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/applications/">dashboard application guide</a> describes its registry and controls. Keep these two layers separate when explaining a discovery result.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="define-a-completed-discovery-review">Define a completed discovery review<a href="https://serverappmanager.ommrudraksha.com/blog/discover-aspnet-core-systemd-services/#define-a-completed-discovery-review" class="hash-link" aria-label="Direct link to Define a completed discovery review" title="Direct link to Define a completed discovery review" translate="no">​</a></h2>
<p>A complete result is an accurate local entry for a known service, with a verified identity and honest supplementary metadata. It includes an understanding of what remains unknown.</p>
<p>For your first session, register one application and prove that its status and logs match the expected service. Add the next application only after that workflow is clear. This small review discipline prevents a convenient discovery screen from becoming an unverified list of production controls.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label=".NET on Ubuntu" term=".NET on Ubuntu"/>
        <category label="systemd" term="systemd"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Find the first error in an ASP.NET Core systemd journal]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Use bounded per-service logs, timestamps and surrounding messages to identify the first useful failure.]]></summary>
        <content type="html"><![CDATA[<p>A failed application can produce pages of repeated messages. The most useful entry is often the first meaningful failure in a startup attempt, followed by enough context to explain which layer stopped working.</p>
<p>Server App Manager provides bounded recent journal views for registered applications. This guide explains how to use those views, distinguish missing logs from a quiet service, and preserve a small amount of useful evidence. The sample service name is <code>demo-web.service</code>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="identify-the-service-and-time-window">Identify the service and time window<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#identify-the-service-and-time-window" class="hash-link" aria-label="Direct link to Identify the service and time window" title="Direct link to Identify the service and time window" translate="no">​</a></h2>
<p>Start with the exact unit that belongs to the application. A public URL and a friendly display name are useful context, but the journal query needs the correct service identity.</p>
<p>Ask when the symptom began and whether a deployment, restart or dependency change happened nearby. An approximate timestamp makes a short recent slice much easier to interpret.</p>
<p>Record the current state and main PID before making changes. Restarting immediately can create another startup sequence and make it harder to distinguish the failure you originally wanted to inspect from a later attempt.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="open-a-bounded-journal-view">Open a bounded journal view<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#open-a-bounded-journal-view" class="hash-link" aria-label="Direct link to Open a bounded journal view" title="Direct link to Open a bounded journal view" translate="no">​</a></h2>
<p>In the local dashboard, choose <strong>Logs</strong> for the registered application. Start with the last 100 entries. If the relevant startup attempt is older, expand to 250 or 500.</p>
<p>These are bounded views, not a complete historical log archive. Search and level filters work on the messages currently loaded. A missing search result therefore does not prove that the event never occurred.</p>
<p>The dashboard uses structured journal data to retain timestamps and classify entries. It also bounds command output. If output reaches a limit, read the displayed notice before assuming the visible list contains every requested entry.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="understand-the-independent-terminal-comparison">Understand the independent terminal comparison<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#understand-the-independent-terminal-comparison" class="hash-link" aria-label="Direct link to Understand the independent terminal comparison" title="Direct link to Understand the independent terminal comparison" translate="no">​</a></h2>
<p>For an authorized read-only comparison on the same sample unit, a conventional journal query is:</p>
<div class="language-sh codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#bfc7d5;--prism-background-color:#292d3e"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-sh codeBlock_bY9V thin-scrollbar" style="color:#bfc7d5;background-color:#292d3e"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#bfc7d5"><span class="token plain">journalctl -u demo-web.service -n 100 --no-pager -o short-iso</span><br></div></code></pre></div></div>
<p>This asks for a recent per-unit slice in a readable timestamp format. It is a comparison aid, not the exact structured-output command used internally by every dashboard revision.</p>
<p>The <a href="https://www.freedesktop.org/software/systemd/man/latest/journalctl.html" target="_blank" rel="noopener noreferrer" class="">journalctl manual</a> documents per-unit matching, recent-entry selection and output formats. Use the same unit and similar sample time when comparing two views, or new messages can make the lists legitimately different.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-the-first-useful-failure">Read the first useful failure<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#read-the-first-useful-failure" class="hash-link" aria-label="Direct link to Read the first useful failure" title="Direct link to Read the first useful failure" translate="no">​</a></h2>
<p>Repeated framework shutdown or retry messages can be consequences of an earlier cause. Search for the first clear exception, bind failure or configuration error in the startup attempt.</p>
<p>Then read the surrounding messages. A preceding information entry might identify the environment or the startup stage. A following message might explain whether the service exited or retried.</p>
<p>Do not automatically select the earliest red row across the entire loaded history. You want the earliest useful failure in the relevant attempt. An old unrelated error from a previous deployment can otherwise send the investigation in the wrong direction.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-filters-to-navigate-then-restore-context">Use filters to navigate, then restore context<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#use-filters-to-navigate-then-restore-context" class="hash-link" aria-label="Direct link to Use filters to navigate, then restore context" title="Direct link to Use filters to navigate, then restore context" translate="no">​</a></h2>
<p>An error filter is useful for finding a candidate message quickly. It can also hide the information entries that explain what the application was doing.</p>
<p>After locating the candidate, return to the broader view and inspect nearby messages. Search for a short stable phrase from the error rather than a private account name or a long connection string.</p>
<p>Priorities and application text conventions can differ. The source preview considers structured priority and recognizable logging prefixes. A color is a navigation aid, not proof that the application correctly assigned severity to every event.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="try-a-port-conflict-example-in-a-lab">Try a port-conflict example in a lab<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#try-a-port-conflict-example-in-a-lab" class="hash-link" aria-label="Direct link to Try a port-conflict example in a lab" title="Direct link to Try a port-conflict example in a lab" translate="no">​</a></h2>
<p>A useful exercise uses a disposable .NET service whose configured listener conflicts with another known sample listener. Start the exercise only in that isolated environment with an understood recovery plan.</p>
<p>Observe the application status and load its recent logs. Look for the earliest message describing the listener problem, then note the subsequent shutdown or failed-start behavior.</p>
<p>The article does not provide recorded output from a real machine. Write down the message your own lab produces and the versions involved. Different frameworks and logging settings can phrase the same class of failure differently.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="confirm-one-narrow-explanation">Confirm one narrow explanation<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#confirm-one-narrow-explanation" class="hash-link" aria-label="Direct link to Confirm one narrow explanation" title="Direct link to Confirm one narrow explanation" translate="no">​</a></h2>
<p>Once you have a candidate cause, choose a read-only check that can support or contradict it. For a suspected listener conflict, inspect the known lab port with the server owner's normal diagnostic tools.</p>
<p>For a missing dependency, verify the intended dependency's state rather than restarting every service. For a configuration problem, ask the application's owner to review the relevant setting through their approved process.</p>
<p>A strong note distinguishes the symptom from the explanation: the service failed to start; its first useful log reported a particular problem; an independent observation agreed with that problem. Avoid skipping straight from an error word to an unrelated repair.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="handle-empty-output-and-permission-errors">Handle empty output and permission errors<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#handle-empty-output-and-permission-errors" class="hash-link" aria-label="Direct link to Handle empty output and permission errors" title="Direct link to Handle empty output and permission errors" translate="no">​</a></h2>
<p>A quiet journal slice can have several explanations. The selected unit may be wrong, the relevant event may be outside the recent bound, the application may log elsewhere, or your account may not have access.</p>
<p>Read the dashboard error before classifying the situation. A denied query is different from a successful query returning no matching entries.</p>
<p>Do not treat a missing log as proof that an app did nothing. Confirm the launch and logging model with its owner. If broader journal access is needed, follow the owner's policy rather than changing group membership or sudo rules just to bypass an unexplained error.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="keep-timestamps-useful-across-machines">Keep timestamps useful across machines<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#keep-timestamps-useful-across-machines" class="hash-link" aria-label="Direct link to Keep timestamps useful across machines" title="Direct link to Keep timestamps useful across machines" translate="no">​</a></h2>
<p>Your PC, the server and application messages can display time differently. The journal's event timestamp and a timestamp embedded inside message text are not automatically the same field.</p>
<p>When recording an incident, include a timezone and preserve enough detail to correlate observations. State whether the time came from the dashboard, a journal entry or a separately checked endpoint.</p>
<p>If two views appear out of order, compare the actual event fields and sample bounds before deciding the logger is broken. The dashboard's recent-entry display can change when new messages arrive between refreshes.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="treat-redaction-as-an-aid-not-a-guarantee">Treat redaction as an aid, not a guarantee<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#treat-redaction-as-an-aid-not-a-guarantee" class="hash-link" aria-label="Direct link to Treat redaction as an aid, not a guarantee" title="Direct link to Treat redaction as an aid, not a guarantee" translate="no">​</a></h2>
<p>The source preview renders log messages as text and suppresses messages matching recognizable secret patterns. This can hide a message that looks relevant because the same line also contains sensitive content.</p>
<p>The suppression is intentional, but it cannot establish that every visible message is safe for public sharing. Some secrets have no recognizable name or format.</p>
<p>Read an excerpt before putting it in an issue. Replace hostnames and account identifiers when they are unnecessary. If the hidden message is essential, use the authorized server operator's own journal workflow and the project's private reporting route where appropriate.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="preserve-a-small-useful-incident-note">Preserve a small, useful incident note<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#preserve-a-small-useful-incident-note" class="hash-link" aria-label="Direct link to Preserve a small, useful incident note" title="Direct link to Preserve a small, useful incident note" translate="no">​</a></h2>
<p>Record the unit, environment, time window, observed state, first useful failure and the supporting read-only check. Include the source revision if the dashboard view itself behaved unexpectedly.</p>
<p>A short sanitized excerpt with its context is often more useful than a large unreviewed log attachment. Avoid copying environment variables or entire configuration dumps into an issue.</p>
<p>If a change is later authorized, record it separately from the inspection. This keeps the investigation understandable: what you saw first, what you concluded, which action was approved, and how you checked the result.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="know-when-the-dashboard-slice-is-enough">Know when the dashboard slice is enough<a href="https://serverappmanager.ommrudraksha.com/blog/find-first-aspnet-core-journal-error/#know-when-the-dashboard-slice-is-enough" class="hash-link" aria-label="Direct link to Know when the dashboard slice is enough" title="Direct link to Know when the dashboard slice is enough" translate="no">​</a></h2>
<p>A 500-entry recent view is convenient for routine triage, but some incidents need a longer history or application-specific diagnostics. Use the server owner's established tools for that deeper investigation.</p>
<p>The dashboard's job is to help you find the next useful question quickly. It should not encourage a claim that every failure has been ruled out simply because the loaded window is short or quiet.</p>
<p>Read the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/logs/">logs guide</a>, <a class="" href="https://serverappmanager.ommrudraksha.com/docs/troubleshooting/">troubleshooting guide</a> and <a href="https://github.com/OmmLabs/MyServerManager/blob/main/src/MyServerManager/Services/JournalService.cs" target="_blank" rel="noopener noreferrer" class="">journal implementation</a> for the current limits and display behavior.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label="Operations" term="Operations"/>
        <category label=".NET on Ubuntu" term=".NET on Ubuntu"/>
        <category label="systemd" term="systemd"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Manage Ubuntu services from Windows using the SSH you already have]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Follow the local PC-to-SSH workflow to discover a service, inspect its logs and check website health.]]></summary>
        <content type="html"><![CDATA[<p>A website incident often starts with a small question: is the application actually running? On a Windows PC, answering it can mean opening SSH, finding the right unit name, checking recent logs and remembering which local port belongs to which site. Server App Manager puts those related observations in one local dashboard.</p>
<p>This guide follows the current source preview from download to one registered application. It uses <code>user@server.example.com</code> and <code>demo-web.service</code> as placeholders. The walkthrough is a reproducible exercise, not a report of measurements from a production server.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="understand-the-three-places-involved">Understand the three places involved<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#understand-the-three-places-involved" class="hash-link" aria-label="Direct link to Understand the three places involved" title="Direct link to Understand the three places involved" translate="no">​</a></h2>
<p>Your browser opens the dashboard on your own computer. An ASP.NET Core process on that computer serves the interface and holds the active SSH connection. Ubuntu continues running its existing applications, systemd and journal.</p>
<p>The public project website has a different job: it provides downloads and instructions. Opening this article does not connect to your server. Likewise, entering a public website URL in the dashboard is a health-check setting, not a replacement for the SSH address used at sign-in.</p>
<p>This separation explains several otherwise confusing behaviors. Closing a browser tab does not necessarily stop the local process. Quitting the local dashboard ends your monitoring session, while Ubuntu applications continue under their existing service manager. A restart button in the dashboard is a separate, explicit request concerning a registered service.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="gather-the-information-before-launching">Gather the information before launching<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#gather-the-information-before-launching" class="hash-link" aria-label="Direct link to Gather the information before launching" title="Direct link to Gather the information before launching" translate="no">​</a></h2>
<p>Start with an SSH account that already works from your PC. Obtain its username, hostname or address, and any custom SSH port. Also obtain the server host-key fingerprint from a trusted console or the administrator responsible for that machine.</p>
<p>For your first application, identify its actual canonical systemd service name. A friendly business name or website domain is not enough. If you know only the site's public address, ask its operator which unit serves it. A server can host several applications with similar deployment names.</p>
<p>Check the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/compatibility/">compatibility guide</a> for current preview requirements. The Windows source workflow needs the .NET 10 SDK. Operations such as restarting services and reading particular journal entries depend on your existing Ubuntu permissions. The dashboard does not grant those permissions during setup.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="get-the-current-source">Get the current source<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#get-the-current-source" class="hash-link" aria-label="Direct link to Get the current source" title="Direct link to Get the current source" translate="no">​</a></h2>
<p>Use the <a class="" href="https://serverappmanager.ommrudraksha.com/download/">download page</a> to obtain the application source ZIP, then extract it into a folder on your PC. The current ZIP points to the main branch, so record the revision if you need to reproduce an evaluation later.</p>
<p>Inside the extracted folder, double-click <strong>Create-Desktop-Shortcut.cmd</strong>. The helper builds a local copy, checks local HTTPS certificate availability and creates the Server App Manager desktop shortcut. Read any certificate trust prompt as a local Windows setup action.</p>
<p>If you prefer a source command, the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/quickstart/">quickstart</a> gives the PowerShell alternative. Keep that command window open while a direct source run is active. The shortcut instead provides a tray menu for opening and quitting the local app.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="start-the-dashboard-on-your-pc">Start the dashboard on your PC<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#start-the-dashboard-on-your-pc" class="hash-link" aria-label="Direct link to Start the dashboard on your PC" title="Direct link to Start the dashboard on your PC" translate="no">​</a></h2>
<p>Open the new desktop shortcut. The usual browser address is <code>https://localhost:7300</code>. Here, localhost means the computer on which the browser is running.</p>
<p>A browser connection error at this address usually concerns local startup, the port or HTTPS trust. It does not establish that Ubuntu is unavailable. Check whether the local app is running before troubleshooting the remote server.</p>
<p>The tray icon offers <strong>Open dashboard</strong> and <strong>Quit Server App Manager</strong>. After restarting Windows, launch the shortcut again. The source preview does not promise automatic startup at Windows sign-in. Keeping this startup model clear helps avoid interpreting an absent local page as a failure of a hosted application.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="verify-the-ssh-endpoint">Verify the SSH endpoint<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#verify-the-ssh-endpoint" class="hash-link" aria-label="Direct link to Verify the SSH endpoint" title="Direct link to Verify the SSH endpoint" translate="no">​</a></h2>
<p>Enter <code>user@server.example.com</code> on first run. If the existing SSH service uses a custom port, the dashboard accepts a value such as <code>user@server.example.com:2222</code>.</p>
<p>The app shows the SSH host-key fingerprint before asking you to trust the endpoint. Compare the complete fingerprint and its key type with the trusted information you collected. Do not treat a successful network connection as proof that it reached the intended server.</p>
<p>After confirmation, enter the Ubuntu account's SSH password. A successful first sign-in saves the endpoint and verified host identity locally. Later sign-ins verify that saved identity again. The current preview uses SSH password authentication; dashboard key authentication is separate roadmap work.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="find-an-existing-application">Find an existing application<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#find-an-existing-application" class="hash-link" aria-label="Direct link to Find an existing application" title="Direct link to Find an existing application" translate="no">​</a></h2>
<p>Open <strong>Applications</strong> and choose <strong>Find apps</strong>. The source preview looks for recognizable .NET service launch patterns among loaded systemd units. A discovery result is a candidate to inspect.</p>
<p>Review the canonical service name, any detected deployment metadata and the visible listening port. Confirm that they belong to the intended application. A background worker can be a valid .NET service while exposing no HTTP listener.</p>
<p>Supply a descriptive display name and, for a public website, its actual HTTP or HTTPS address. The website address is not inferred solely from a listening port. Multiple public domains can share a proxy, and application ports can be private to the host.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="register-only-what-you-intend-to-manage">Register only what you intend to manage<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#register-only-what-you-intend-to-manage" class="hash-link" aria-label="Direct link to Register only what you intend to manage" title="Direct link to Register only what you intend to manage" translate="no">​</a></h2>
<p>Choose <strong>Review and add</strong>, check the proposed fields and save the entry. Registration adds it to your local dashboard registry. It does not create or edit a systemd unit.</p>
<p>For an unrecognized launch wrapper, manual registration can still be appropriate after verifying the real service. Read the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/applications/">application guide</a> rather than inventing a port or deployment path to fill a blank field.</p>
<p>The enabled setting and display order help organize the list. Keep environment labels explicit when names are similar. An entry called “Demo website — test” is easier to distinguish from another environment than two entries with the same friendly name.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="inspect-before-using-the-controls">Inspect before using the controls<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#inspect-before-using-the-controls" class="hash-link" aria-label="Direct link to Inspect before using the controls" title="Direct link to Inspect before using the controls" translate="no">​</a></h2>
<p>Open the registered application's status and logs first. Note the service state, main PID, available memory readings and any recent failure. Missing measurements appear as N/A; that is different from a measured zero.</p>
<p>The <strong>Logs</strong> view loads a bounded slice of recent journal entries. Search and filter within those loaded messages. Read surrounding information entries as well as errors, because the startup sequence can explain which stage failed.</p>
<p>Only use a management action when it addresses a known operational need. Stop and restart require confirmation, and the service may become unavailable during the change. On a shared host, check dependencies and ownership before confirming. Practice the workflow with a disposable service first.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-website-health-as-an-independent-signal">Read website health as an independent signal<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#read-website-health-as-an-independent-signal" class="hash-link" aria-label="Direct link to Read website health as an independent signal" title="Direct link to Read website health as an independent signal" translate="no">​</a></h2>
<p>A running service and a healthy public URL answer different questions. Open Website Health for the registered address and note the HTTP result, response time and check timestamp.</p>
<p>A failed public check can involve DNS, TLS, networking, a reverse proxy or the application's response. A successful check can reflect one public endpoint without proving that every feature works. For a background worker, HTTP availability may not apply at all.</p>
<p>When a symptom appears, write down both observations at nearby times: for example, the actual service state and the actual HTTP response. Avoid replacing this evidence with a broad conclusion such as “the whole server is down.”</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="finish-a-session-deliberately">Finish a session deliberately<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#finish-a-session-deliberately" class="hash-link" aria-label="Direct link to Finish a session deliberately" title="Direct link to Finish a session deliberately" translate="no">​</a></h2>
<p>Sign out when you finish inspecting the server. The local SSH session ends and its in-memory credential is cleared through the application's connection lifecycle. Use the tray menu if you also want to stop the local dashboard process.</p>
<p>Registered applications and audit history remain local for the saved server. <strong>Remove</strong> beside an application unregisters that local entry. <strong>Remove server</strong> is a separate authenticated setting that closes the connection and archives the registration's data.</p>
<p>Review <a class="" href="https://serverappmanager.ommrudraksha.com/docs/update-and-remove/">update and removal instructions</a> before moving or deleting local state. Treat backups as private operational data, even when they contain no saved SSH password.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="keep-a-useful-first-session-record">Keep a useful first-session record<a href="https://serverappmanager.ommrudraksha.com/blog/manage-ubuntu-services-from-windows/#keep-a-useful-first-session-record" class="hash-link" aria-label="Direct link to Keep a useful first-session record" title="Direct link to Keep a useful first-session record" translate="no">​</a></h2>
<p>For an evaluation, record the source revision, Windows version, Ubuntu version, registered sample unit and which reads were available. Note permission-denied and unavailable readings separately from application failures.</p>
<p>A useful completed exercise has a narrow outcome: you can start the dashboard, verify the endpoint, register the correct existing service, inspect its status and logs, and distinguish its process state from website health. That is a stronger starting point than adding many unverified services at once.</p>
<p>For the product-specific behavior described here, consult the <a href="https://github.com/OmmLabs/MyServerManager/blob/main/README.md" target="_blank" rel="noopener noreferrer" class="">application README</a> and <a href="https://github.com/OmmLabs/MyServerManager/blob/main/SECURITY.md" target="_blank" rel="noopener noreferrer" class="">security notes</a>. The hosting relationship between ASP.NET Core, systemd and a proxy is documented in <a href="https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-10.0" target="_blank" rel="noopener noreferrer" class="">Microsoft's Linux hosting guide</a>.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label="SSH" term="SSH"/>
        <category label="Operations" term="Operations"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Fix an Nginx 502 in front of an ASP.NET Core app]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Trace a gateway failure through the public URL, proxy and application listener before choosing a repair.]]></summary>
        <content type="html"><![CDATA[<p>An Nginx 502 response tells you that a gateway request failed. It does not identify, by itself, whether the backing ASP.NET Core service stopped, the proxy points at the wrong listener, or another upstream problem occurred.</p>
<p>This guide develops a read-first investigation using a disposable application called <code>demo-web.service</code>. It shows how Server App Manager's separate service, log and website views help you narrow the problem without treating a restart as the first diagnostic step.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="draw-the-request-path-you-are-investigating">Draw the request path you are investigating<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#draw-the-request-path-you-are-investigating" class="hash-link" aria-label="Direct link to Draw the request path you are investigating" title="Direct link to Draw the request path you are investigating" translate="no">​</a></h2>
<p>Write the intended route as a short sequence: public URL, Nginx virtual host, configured upstream, application listener and relevant dependencies.</p>
<p>The browser's public HTTPS port is often different from the internal application port. A unit name can differ from both the website name and deployment folder. Keep those identities separate in your notes.</p>
<p>Use the route actually configured on the server. Do not copy another application's port simply because both applications run .NET. On a shared host, an incorrect assumption can direct testing or maintenance at an unrelated service.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="confirm-the-public-observation">Confirm the public observation<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#confirm-the-public-observation" class="hash-link" aria-label="Direct link to Confirm the public observation" title="Direct link to Confirm the public observation" translate="no">​</a></h2>
<p>Open Website Health for the affected registered URL. Read the exact response code, error and timestamp. Run a manual check when you need a fresh observation.</p>
<p>A public 502 is different from a DNS failure, TLS error or connection timeout. Preserve that distinction before looking for application logs. If the browser and dashboard differ, compare the requested path and the network from which each request originated.</p>
<p>The dashboard's probes run from your PC. A public endpoint can therefore be reachable from Ubuntu but unavailable from your network, or the reverse. The location of the observation matters when interpreting a result.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="inspect-the-intended-application-unit">Inspect the intended application unit<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#inspect-the-intended-application-unit" class="hash-link" aria-label="Direct link to Inspect the intended application unit" title="Direct link to Inspect the intended application unit" translate="no">​</a></h2>
<p>Open the registered application's service details. Check its state and main PID before requesting a change.</p>
<p>If the unit is stopped or failed, read its recent journal. Find the first useful startup failure in the relevant attempt. A later retry or shutdown line may describe a consequence rather than the cause.</p>
<p>If the unit is active, continue investigating. An active service is not a promise that it is listening on the port Nginx expects, returning a correct response, or ready to serve a particular application route.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="compare-the-listener-with-the-upstream">Compare the listener with the upstream<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#compare-the-listener-with-the-upstream" class="hash-link" aria-label="Direct link to Compare the listener with the upstream" title="Direct link to Compare the listener with the upstream" translate="no">​</a></h2>
<p>With the server owner's read-only diagnostic workflow, identify the actual local listener associated with the application. Compare its address and port with the proxy's configured destination.</p>
<p>A unit that listens on one port while the proxy forwards to another gives a specific inconsistency to investigate. Likewise, an IPv4 versus IPv6 binding difference or a socket path can matter in an existing configuration.</p>
<p>The <a href="https://nginx.org/en/docs/http/ngx_http_proxy_module.html" target="_blank" rel="noopener noreferrer" class="">Nginx proxy module documentation</a> describes upstream forwarding. Keep the article's example ports out of production configuration: the intended destination must come from your own reviewed installation.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-a-small-nginx-error-excerpt">Read a small Nginx error excerpt<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#read-a-small-nginx-error-excerpt" class="hash-link" aria-label="Direct link to Read a small Nginx error excerpt" title="Direct link to Read a small Nginx error excerpt" translate="no">​</a></h2>
<p>Ask the authorized operator for the error-log entries corresponding to the failed request time and virtual host. Keep the excerpt bounded and sanitized.</p>
<p>Compare the upstream target and failure description with the listener observation. A connection refusal, upstream closure and timeout can point toward different next checks, even when the browser reports a similar gateway symptom.</p>
<p>The dashboard's application journal view is not a general Nginx error-log editor or unrestricted terminal. Use the operator's established log access for the proxy layer. Do not assume the absence of an application error means the proxy successfully reached that application.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-a-stopped-service-example-in-a-lab">Use a stopped-service example in a lab<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#use-a-stopped-service-example-in-a-lab" class="hash-link" aria-label="Direct link to Use a stopped-service example in a lab" title="Direct link to Use a stopped-service example in a lab" translate="no">​</a></h2>
<p>For a controlled exercise, begin with a working disposable site and a known systemd service. Record the public response, the unit state and the local listener.</p>
<p>The lab owner can then stop the sample service as an explicitly approved test. Observe the changed service state and the public result. Record what the actual installation reports rather than expecting every possible setup to produce an identical page or message.</p>
<p>Restore the sample through the authorized maintenance procedure and verify both layers again. This demonstrates a relationship between a missing backing process and a gateway failure without presenting fictional production evidence.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-a-wrong-upstream-example-separately">Use a wrong-upstream example separately<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#use-a-wrong-upstream-example-separately" class="hash-link" aria-label="Direct link to Use a wrong-upstream example separately" title="Direct link to Use a wrong-upstream example separately" translate="no">​</a></h2>
<p>A second disposable exercise can point a lab proxy at an unused local port while leaving the sample application running on its real listener.</p>
<p>The distinguishing evidence should be clear: the service is active, its real local endpoint answers, and the proxy's destination does not match that endpoint. Treat that as a configuration investigation rather than a reason to restart the healthy application repeatedly.</p>
<p>Only the lab owner should edit the configuration for this exercise. Keep a known-good copy and a recovery plan. The dashboard intentionally does not provide an Nginx configuration editor.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="choose-the-repair-from-the-evidence">Choose the repair from the evidence<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#choose-the-repair-from-the-evidence" class="hash-link" aria-label="Direct link to Choose the repair from the evidence" title="Direct link to Choose the repair from the evidence" translate="no">​</a></h2>
<p>If an application failed to start, address the identified application problem through its owner. If the configured upstream is wrong, review the proxy change through the server's existing configuration process.</p>
<p>A dependency failure can leave a listener present while application requests still fail. In that case, inspect the dependency through the appropriate operator rather than broadening the restart to unrelated services.</p>
<p>Record why the proposed change follows from the observations. This short explanation makes the maintenance review much more useful than a list of commands executed without their intended effect.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="validate-before-applying-a-proxy-change">Validate before applying a proxy change<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#validate-before-applying-a-proxy-change" class="hash-link" aria-label="Direct link to Validate before applying a proxy change" title="Direct link to Validate before applying a proxy change" translate="no">​</a></h2>
<p>When a proxy configuration change is authorized, validate the installed Nginx configuration using the verified binary and layout. The dashboard's optional Nginx controls perform configuration validation before a reload or restart.</p>
<p>A validation failure is a reason to stop and inspect the error, not a prompt to bypass the test. A successful syntax check also does not prove the intended website-to-upstream mapping is correct.</p>
<p>The <a href="https://nginx.org/en/docs/control.html" target="_blank" rel="noopener noreferrer" class="">Nginx control documentation</a> describes configuration reloading and worker behavior. Check the current installation's supported management path with its owner before choosing between reload and restart.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="retest-the-same-meaningful-path">Retest the same meaningful path<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#retest-the-same-meaningful-path" class="hash-link" aria-label="Direct link to Retest the same meaningful path" title="Direct link to Retest the same meaningful path" translate="no">​</a></h2>
<p>After the authorized repair, repeat the checks that established the problem. Compare the unit state, actual listener, proxy destination and public URL.</p>
<p>Use the same meaningful application path where possible. A static landing page can answer while a database-backed page still fails. Conversely, an application can intentionally return an authentication response on a protected route.</p>
<p>The result you need is the response expected for that particular route and caller. Keep “HTTP request completed” separate from “the application function recovered” in the incident record.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="handle-a-timeout-without-compounding-the-incident">Handle a timeout without compounding the incident<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#handle-a-timeout-without-compounding-the-incident" class="hash-link" aria-label="Direct link to Handle a timeout without compounding the incident" title="Direct link to Handle a timeout without compounding the incident" translate="no">​</a></h2>
<p>If an operation times out, inspect the actual service and pending work before repeating it. A client deadline can expire while a remote systemd job continues.</p>
<p>Recheck timestamps when reading logs. A newly visible entry may describe the original request, a later health probe or a fresh startup attempt. Correlate observations before deciding another component must now be restarted.</p>
<p>Escalate with the smallest useful package of evidence: target unit and environment, public response, sanitized proxy excerpt, observed listener and the exact operation result. Keep credentials and full configuration dumps out of public issues.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="close-with-a-cause-and-a-verified-outcome">Close with a cause and a verified outcome<a href="https://serverappmanager.ommrudraksha.com/blog/fix-nginx-502-aspnet-core-ubuntu/#close-with-a-cause-and-a-verified-outcome" class="hash-link" aria-label="Direct link to Close with a cause and a verified outcome" title="Direct link to Close with a cause and a verified outcome" translate="no">​</a></h2>
<p>A useful incident record explains which part of the path was wrong and what evidence supported the conclusion. It identifies the approved change and the checks that passed afterwards.</p>
<p>For an unresolved case, state the remaining uncertainty just as clearly. “The application listener answers locally, but the proxy's upstream request still times out” gives the next operator a better starting point than “Nginx is broken.”</p>
<p>Continue with the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/nginx/">Nginx guide</a>, <a class="" href="https://serverappmanager.ommrudraksha.com/docs/website-health/">Website Health guide</a> and <a class="" href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/">service restart walkthrough</a> for the corresponding dashboard workflows.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label=".NET on Ubuntu" term=".NET on Ubuntu"/>
        <category label="Operations" term="Operations"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Restart an ASP.NET Core service with a short safety checklist]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Confirm the target and impact, restart once, then verify systemd state, journal entries and public website behavior.]]></summary>
        <content type="html"><![CDATA[<p>A restart can be the right operation, but it is useful only when you know which service you are restarting and what result you expect. A green command result alone cannot establish that customers can use the application again.</p>
<p>This guide follows a deliberate restart of <code>demo-web.service</code> in a disposable Ubuntu environment. It explains the dashboard's confirmation and result flow, how to gather a baseline, and what to do when the result is unclear.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="decide-why-a-restart-is-needed">Decide why a restart is needed<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#decide-why-a-restart-is-needed" class="hash-link" aria-label="Direct link to Decide why a restart is needed" title="Direct link to Decide why a restart is needed" translate="no">​</a></h2>
<p>Write down the symptom and the proposed reason for restarting. Examples include applying an already authorized deployment or recovering a service after an identified transient failure.</p>
<p>If you have no evidence about the cause, begin with status and logs. Repeated restarts can erase the useful context of a short-lived failure, replace a PID you were investigating or create an additional interruption.</p>
<p>Define the desired outcome in observable terms. “The canonical unit reaches its expected state, its startup error stops recurring, and the public endpoint passes a representative check” is more useful than “click restart until it looks green.”</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="confirm-the-exact-target">Confirm the exact target<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#confirm-the-exact-target" class="hash-link" aria-label="Direct link to Confirm the exact target" title="Direct link to Confirm the exact target" translate="no">​</a></h2>
<p>In Applications, verify the display name, environment and canonical unit name together. Similar blue, green, staging and production names deserve an explicit second look.</p>
<p>Confirm that the entry belongs to the site or worker under investigation. A public hostname is not itself a systemd identity. If the mapping is uncertain, ask the owner before taking action.</p>
<p>The registry's port and path are metadata. They can help identify the target, but the management action is directed at the registered unit. Read the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/applications/">application guide</a> if an entry needs correcting before the maintenance operation.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="consider-the-effect-beyond-the-one-process">Consider the effect beyond the one process<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#consider-the-effect-beyond-the-one-process" class="hash-link" aria-label="Direct link to Consider the effect beyond the one process" title="Direct link to Consider the effect beyond the one process" translate="no">​</a></h2>
<p>A web application may depend on a shared database, cache, identity provider or proxy. Its users may have in-flight requests, and a worker may be processing a job.</p>
<p>The service unit itself can define ordering and relationships with other units. Your server owner should understand those relationships before approving control.</p>
<p>For this walkthrough, use a disposable sample service with a known owner and a simple endpoint. The article is a maintenance exercise, not blanket authorization to restart services on a shared production host.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="capture-a-small-baseline">Capture a small baseline<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#capture-a-small-baseline" class="hash-link" aria-label="Direct link to Capture a small baseline" title="Direct link to Capture a small baseline" translate="no">​</a></h2>
<p>Before confirming the operation, record the current service state, main PID, available memory and approximate time. Open recent logs and note the last meaningful failure or successful startup message.</p>
<p>Check the configured public URL separately. Capture the actual status and time rather than assuming the website failed because the process looks unhealthy.</p>
<p>A baseline makes the follow-up interpretable. If the public endpoint already worked before maintenance, you should know whether it remains available. If a request failed beforehand, you can compare the same path afterwards instead of testing an unrelated page.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="check-that-the-operation-is-authorized">Check that the operation is authorized<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#check-that-the-operation-is-authorized" class="hash-link" aria-label="Direct link to Check that the operation is authorized" title="Direct link to Check that the operation is authorized" translate="no">​</a></h2>
<p>The dashboard uses the Ubuntu account's existing permissions. A successful SSH sign-in does not guarantee permission to restart every service.</p>
<p>If a prior action returned permission denied, follow the server owner's policy instead of trying increasingly broad commands. The <a class="" href="https://serverappmanager.ommrudraksha.com/docs/permissions/">permissions guide</a> explains the relationship between the local app and the remote account.</p>
<p>The dashboard's bounded commands and registry checks reduce accidental input freedom, but they do not replace responsibility for the target service. Keep the permission question resolved before the maintenance window begins.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-and-use-the-confirmation">Read and use the confirmation<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#read-and-use-the-confirmation" class="hash-link" aria-label="Direct link to Read and use the confirmation" title="Direct link to Read and use the confirmation" translate="no">​</a></h2>
<p>Choose <strong>Restart</strong> for the intended application. Read the confirmation, including its application name and temporary availability impact.</p>
<p>Cancel once during a lab exercise to understand that path. A cancellation should leave the service unchanged. Then repeat the exercise only when you actually intend to perform the restart.</p>
<p>After confirming, wait for the operation result. The interface prevents accidental repeated requests during an active operation, and the application coordinates conflicting management changes. Opening another tab is not a useful way to accelerate a service that is still starting.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="understand-what-the-result-describes">Understand what the result describes<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#understand-what-the-result-describes" class="hash-link" aria-label="Direct link to Understand what the result describes" title="Direct link to Understand what the result describes" translate="no">​</a></h2>
<p>The dashboard reports the command's actual outcome and refreshes the unit status. This is different from reporting success merely because it accepted a button click.</p>
<p>A systemd restart normally involves stopping and starting the unit. Its exact effects depend on the service and relationships already configured on the host. The <a href="https://www.freedesktop.org/software/systemd/man/latest/systemctl.html#restart%20PATTERN%E2%80%A6" target="_blank" rel="noopener noreferrer" class="">systemctl restart documentation</a> describes that operation.</p>
<p>For product-specific execution and coordination details, read the <a href="https://github.com/OmmLabs/MyServerManager/blob/main/src/MyServerManager/Services/ApplicationManagement.cs" target="_blank" rel="noopener noreferrer" class="">management implementation</a>. Match your interpretation to the source revision in use.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="verify-service-startup-after-the-command">Verify service startup after the command<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#verify-service-startup-after-the-command" class="hash-link" aria-label="Direct link to Verify service startup after the command" title="Direct link to Verify service startup after the command" translate="no">​</a></h2>
<p>Read the refreshed state and inspect recent journal messages. A new PID can support the observation that a process was replaced, but PID change alone is not an application readiness test.</p>
<p>Look for the expected startup stage and the absence of a repeated failure loop. Give the application the time its normal startup requires. Avoid turning a polling interval into a promise about recovery speed.</p>
<p>If the unit is active but the application keeps logging a dependency failure, treat that as a separate unresolved condition. Record what is actually working rather than compressing all layers into a single “restarted successfully” statement.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="verify-the-public-endpoint-independently">Verify the public endpoint independently<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#verify-the-public-endpoint-independently" class="hash-link" aria-label="Direct link to Verify the public endpoint independently" title="Direct link to Verify the public endpoint independently" translate="no">​</a></h2>
<p>Use Website Health to check the configured public address after the operation. Note its response code, response time and check timestamp.</p>
<p>A public request can still fail because of Nginx, DNS, TLS or application routing. Conversely, a cached or shallow success response does not validate every database-backed feature.</p>
<p>For an authorized lab test, include one representative application function whose result matters to the maintenance task. Keep it read-only when possible. The dashboard does not log into the application on your behalf or establish that all user journeys recovered.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="handle-a-timeout-by-inspecting-first">Handle a timeout by inspecting first<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#handle-a-timeout-by-inspecting-first" class="hash-link" aria-label="Direct link to Handle a timeout by inspecting first" title="Direct link to Handle a timeout by inspecting first" translate="no">​</a></h2>
<p>A timeout means that the client stopped waiting within its bound. It does not, by itself, prove that no remote work happened.</p>
<p>The unit can still have an active job or be transitioning. Read its actual state and current logs before considering another operation. Record the time at which the original request was made.</p>
<p>If the result remains ambiguous, involve the server operator with the target unit, sanitized error, timestamps and observed state. A second restart should follow a new decision based on evidence, not a reflex response to the first request's timeout message.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="keep-the-audit-record-useful">Keep the audit record useful<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#keep-the-audit-record-useful" class="hash-link" aria-label="Direct link to Keep the audit record useful" title="Direct link to Keep the audit record useful" translate="no">​</a></h2>
<p>Open Audit History and locate the restart entry. Review the target, action, signed-in account, timestamp and result.</p>
<p>Add a short maintenance note outside the dashboard if your team needs to connect the action to a ticket or deployment. Include the before-and-after observations and any remaining problem.</p>
<p>Audit history is local operational data and should remain private. Share a minimal sanitized excerpt when reporting a defect. The <a class="" href="https://serverappmanager.ommrudraksha.com/docs/audit-history/">audit guide</a> explains retention scope and why an independent copy may be needed for organizational requirements.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="end-with-a-specific-recovery-statement">End with a specific recovery statement<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-aspnet-core-systemd-service/#end-with-a-specific-recovery-statement" class="hash-link" aria-label="Direct link to End with a specific recovery statement" title="Direct link to End with a specific recovery statement" translate="no">​</a></h2>
<p>A useful completion note identifies the service and environment, the one operation performed and the evidence checked afterwards. It also states any remaining issue explicitly.</p>
<p>In a lab, you should be able to demonstrate a cancelled confirmation, an authorized restart, a real command result and a separate website check. For failure exercises, distinguish denied permission, command timeout and application startup error.</p>
<p>That produces a repeatable maintenance habit: identify, inspect, confirm, observe and record. The interface makes the operation easier to reach; the surrounding evidence makes the result understandable.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label="systemd" term="systemd"/>
        <category label="Operations" term="Operations"/>
        <category label=".NET on Ubuntu" term=".NET on Ubuntu"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Measure the real memory used by an Ubuntu systemd service]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Distinguish cgroup service memory, main-process memory and total server RAM, and understand unavailable measurements.]]></summary>
        <content type="html"><![CDATA[<p>“How much memory is my application using?” sounds like one question. On an Ubuntu server, it can refer to the main process, the whole systemd service, a managed heap or the entire host. Those values describe different scopes.</p>
<p>Server App Manager uses service cgroup measurements where available and displays host RAM separately. This guide shows how to interpret those readings and build a read-only comparison exercise without turning one snapshot into a diagnosis of a memory leak.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="decide-which-scope-you-need">Decide which scope you need<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#decide-which-scope-you-need" class="hash-link" aria-label="Direct link to Decide which scope you need" title="Direct link to Decide which scope you need" translate="no">​</a></h2>
<p>For service operations, begin with the resources attributed to the service and its processes. A main PID is useful for process identity, but its individual memory reading does not automatically include every child.</p>
<p>For a .NET performance investigation, the managed heap can be another useful scope. It still does not represent all native allocations, mappings and other memory associated with the process or service.</p>
<p>At host level, total and available RAM describe the machine's capacity and present state. A dashboard card showing server RAM should never be copied into an individual application's row. Keep the subject of each measurement explicit in notes and screenshots.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="start-from-the-registered-unit">Start from the registered unit<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#start-from-the-registered-unit" class="hash-link" aria-label="Direct link to Start from the registered unit" title="Direct link to Start from the registered unit" translate="no">​</a></h2>
<p>Identify the exact systemd unit whose memory you want to understand. Check its environment and current state before reading a number beside its display name.</p>
<p>A service that is stopped may have no active main process or readable current cgroup. An unknown value is not necessarily zero, and an unavailable peak is not evidence that no peak occurred.</p>
<p>For a lab example, use <code>demo-web.service</code>. Record the unit name, approximate sample time and application revision. This gives each later comparison a stable reference and prevents values from another environment being substituted accidentally.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="discover-the-cgroup-instead-of-guessing-its-directory">Discover the cgroup instead of guessing its directory<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#discover-the-cgroup-instead-of-guessing-its-directory" class="hash-link" aria-label="Direct link to Discover the cgroup instead of guessing its directory" title="Direct link to Discover the cgroup instead of guessing its directory" translate="no">​</a></h2>
<p>A service can be placed below a custom slice or another nested hierarchy. Do not assume every unit lives directly below one fixed system.slice path.</p>
<p>The current dashboard obtains the unit's control-group location and uses validated access to the relevant files. For an independent, authorized read-only inspection, request the location:</p>
<div class="language-sh codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#bfc7d5;--prism-background-color:#292d3e"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-sh codeBlock_bY9V thin-scrollbar" style="color:#bfc7d5;background-color:#292d3e"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#bfc7d5"><span class="token plain">systemctl show demo-web.service -p ControlGroup -p MainPID -p MemoryCurrent -p MemoryPeak</span><br></div></code></pre></div></div>
<p>Use the actual returned group path when locating the service under the mounted cgroup v2 hierarchy. Keep the mount location and unit path as separate pieces of information rather than concatenating a guessed deployment directory.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-the-current-measurement-carefully">Read the current measurement carefully<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#read-the-current-measurement-carefully" class="hash-link" aria-label="Direct link to Read the current measurement carefully" title="Direct link to Read the current measurement carefully" translate="no">​</a></h2>
<p>The cgroup v2 memory controller exposes <code>memory.current</code> for current attributed usage. A peak file may also be available, depending on the host's kernel and accounting support.</p>
<p>The kernel documentation explains these interfaces and their accounting scope. In particular, service-attributed memory is broader than a .NET managed heap. A comparison must keep the controller's meaning rather than treating all accounted bytes as live application objects. See the <a href="https://docs.kernel.org/admin-guide/cgroup-v2.html" target="_blank" rel="noopener noreferrer" class="">cgroup v2 memory documentation</a>.</p>
<p>In the dashboard, open application details and read the current memory, peak, PID and task information together. Treat an unavailable file or unsupported counter as missing evidence. The interface uses N/A rather than filling the gap with host memory.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="keep-units-consistent">Keep units consistent<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#keep-units-consistent" class="hash-link" aria-label="Direct link to Keep units consistent" title="Direct link to Keep units consistent" translate="no">​</a></h2>
<p>Raw Linux counters commonly express memory in bytes. Human-readable displays scale those values for readability.</p>
<p>When making a comparison, note whether the display uses decimal or binary units. One MiB is 1,048,576 bytes; one decimal MB is 1,000,000 bytes. A value labeled casually as “MB” by another tool can create a visible difference even if the underlying counter agrees.</p>
<p>For an exercise, retain the original byte value and write the conversion explicitly. Avoid rounding several times between tools. Compare like-for-like values before interpreting a small difference as a problem in either the application or the dashboard.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="expect-nearby-samples-to-differ">Expect nearby samples to differ<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#expect-nearby-samples-to-differ" class="hash-link" aria-label="Direct link to Expect nearby samples to differ" title="Direct link to Expect nearby samples to differ" translate="no">​</a></h2>
<p>The dashboard and your terminal are unlikely to read a counter at exactly the same moment. An application can allocate, release or cache data between those reads.</p>
<p>Write down nearby timestamps and repeat the observation under a similar workload. A small disagreement between sequential samples is less informative than a persistent difference in scope, unit conversion or cgroup identity.</p>
<p>The dashboard also caches readings between refreshes. Use a manual refresh when checking a specific comparison, then record when it completed. Continuous rapid refreshes create additional work without making two independent samples perfectly simultaneous.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="compare-current-and-peak-without-confusing-them">Compare current and peak without confusing them<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#compare-current-and-peak-without-confusing-them" class="hash-link" aria-label="Direct link to Compare current and peak without confusing them" title="Direct link to Compare current and peak without confusing them" translate="no">​</a></h2>
<p>Current usage answers what the counter attributes now. Peak usage describes a high-water mark over the scope and lifetime represented by that counter.</p>
<p>A peak can stay high after current usage falls. That is expected for a high-water mark and does not mean the application is still consuming the peak amount.</p>
<p>Avoid assuming a peak survived every service restart, cgroup recreation or host reboot. Record the lifecycle surrounding the observation. The source preview displays the available peak and leaves unsupported values as N/A; it does not create a permanent historical chart from a single kernel counter.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-process-details-as-supporting-evidence">Use process details as supporting evidence<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#use-process-details-as-supporting-evidence" class="hash-link" aria-label="Direct link to Use process details as supporting evidence" title="Direct link to Use process details as supporting evidence" translate="no">​</a></h2>
<p>The main PID identifies a process chosen by systemd for the unit. Process counts and task counts describe other aspects of the running service.</p>
<p>A task count should not be interpreted as a request rate. A main-process resident measurement should not be assumed to equal the cgroup total. These are related observations with different purposes.</p>
<p>For a lab comparison, use a service that launches a known child process. Inspect the service-wide reading and the main-process view at nearby times. The goal is to explain the difference in membership and scope, not to force the two tools to report the same number.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-host-ram-separately">Read host RAM separately<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#read-host-ram-separately" class="hash-link" aria-label="Direct link to Read host RAM separately" title="Direct link to Read host RAM separately" translate="no">​</a></h2>
<p>Server Monitoring shows total, used and available RAM for Ubuntu. These measurements are separate from an application's service row.</p>
<p>The host can use memory for the kernel, other services and caches. An application can hold a modest cgroup allocation while the machine has little available RAM because other workloads consume the rest.</p>
<p>The kernel's <a href="https://docs.kernel.org/filesystems/proc.html" target="_blank" rel="noopener noreferrer" class="">procfs documentation</a> describes host and process interfaces. For operational notes, keep host capacity, host availability and service attribution in separate columns. This makes capacity conversations much clearer than reporting a single percentage without saying what it measures.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="investigate-na-before-changing-accounting">Investigate N/A before changing accounting<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#investigate-na-before-changing-accounting" class="hash-link" aria-label="Direct link to Investigate N/A before changing accounting" title="Direct link to Investigate N/A before changing accounting" translate="no">​</a></h2>
<p>An unavailable value may result from an unsupported metric, missing permissions, a stopped service or a file that changed during sampling. Read the unit state and any displayed error before deciding which explanation fits.</p>
<p>Do not change resource accounting or service configuration solely to make a dashboard row look complete. Such changes belong to the server owner and need their own review.</p>
<p>When reporting a measurement problem, include the app revision, kernel and systemd versions, cgroup hierarchy type, unit state and sanitized observation. Share enough structure to explain the missing reading without exposing private paths or unrelated configuration.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="use-a-trend-before-calling-something-a-leak">Use a trend before calling something a leak<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#use-a-trend-before-calling-something-a-leak" class="hash-link" aria-label="Direct link to Use a trend before calling something a leak" title="Direct link to Use a trend before calling something a leak" translate="no">​</a></h2>
<p>A single high reading does not establish a memory leak. Repeated samples under a documented workload can identify a pattern that deserves deeper investigation.</p>
<p>Record startup, warm-up, representative work and quieter periods separately. Note whether a restart or deployment reset the observation. If managed-memory diagnosis is needed, use the application's authorized diagnostic workflow rather than interpreting the cgroup total as a heap dump.</p>
<p>Server App Manager provides a practical service-level view. It is a starting point for resource questions, with <a class="" href="https://serverappmanager.ommrudraksha.com/docs/metrics/">monitoring documentation</a> that keeps measurement scopes explicit.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="finish-the-comparison-with-an-honest-explanation">Finish the comparison with an honest explanation<a href="https://serverappmanager.ommrudraksha.com/blog/measure-systemd-service-memory-cgroup-v2/#finish-the-comparison-with-an-honest-explanation" class="hash-link" aria-label="Direct link to Finish the comparison with an honest explanation" title="Direct link to Finish the comparison with an honest explanation" translate="no">​</a></h2>
<p>A useful result names the unit, control-group identity, sample times, raw units and display conversion. It explains why a process value, a peak or host RAM differs.</p>
<p>If a reading remains unavailable, retain that uncertainty rather than replacing it with an attractive number. Accurate N/A is more useful than a confident measurement of the wrong thing.</p>
<p>For implementation details, inspect the <a href="https://github.com/OmmLabs/MyServerManager/blob/main/src/MyServerManager/Services/CgroupMetrics.cs" target="_blank" rel="noopener noreferrer" class="">service metrics source</a> alongside the exact application revision used for the exercise.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label="Monitoring" term="Monitoring"/>
        <category label="systemd" term="systemd"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Restart SQL Server on Ubuntu with a maintenance checklist]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Plan the impact of a SQL Server restart, confirm it once, and separately verify dependent application recovery.]]></summary>
        <content type="html"><![CDATA[<p>Restarting a shared database service can affect several applications at the same time. A convenient button should make the target and result clearer, while keeping the maintenance decision deliberate.</p>
<p>The local SSH mode in Server App Manager can monitor and restart the canonical <code>mssql-server.service</code> unit when the account is permitted to do so. This guide describes a controlled maintenance exercise on a disposable SQL Server lab, with separate checks for service state, database readiness and application recovery.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="start-with-an-actual-maintenance-reason">Start with an actual maintenance reason<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#start-with-an-actual-maintenance-reason" class="hash-link" aria-label="Direct link to Start with an actual maintenance reason" title="Direct link to Start with an actual maintenance reason" translate="no">​</a></h2>
<p>Write down why a restart is being considered and who owns the decision. A database restart should follow a specific maintenance or recovery need rather than a vague desire to clear an unexplained application error.</p>
<p>Record what success will look like. That should include the expected database availability and the behavior of the applications that depend on it.</p>
<p>If you are investigating an incident, collect the current service state and relevant evidence before starting another lifecycle. Preserve the distinction between an observed database problem and an application symptom that merely mentions a database connection.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="identify-the-dependent-applications">Identify the dependent applications<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#identify-the-dependent-applications" class="hash-link" aria-label="Direct link to Identify the dependent applications" title="Direct link to Identify the dependent applications" translate="no">​</a></h2>
<p>List the applications, workers and scheduled tasks that use the instance. Consider who needs to be notified and which activity should be paused under the team's existing procedure.</p>
<p>An HTTP application can remain running while its database is unavailable. A worker can repeatedly retry a failed connection. Those process states do not tell you that all business operations are safe to resume.</p>
<p>For the lab exercise, use a sample dependent application with a read-only readiness check. Keep its expected response and normal recovery behavior documented before the restart, so the result is not decided after the fact.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="verify-the-supported-lab-installation">Verify the supported lab installation<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#verify-the-supported-lab-installation" class="hash-link" aria-label="Direct link to Verify the supported lab installation" title="Direct link to Verify the supported lab installation" translate="no">​</a></h2>
<p>Use a SQL Server and Ubuntu combination supported by Microsoft for the version under test. Record the actual versions rather than assuming that a generic Ubuntu label establishes compatibility.</p>
<p>Confirm the service identity. The dashboard's database page refers to the fixed canonical SQL Server unit, not a service name entered freely from a browser form.</p>
<p>The app is not a database client and does not modify databases through this management page. The database owner remains responsible for database-level readiness checks, backup policies and any recovery procedure beyond the systemd service operation.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-the-initial-database-service-view">Read the initial database service view<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#read-the-initial-database-service-view" class="hash-link" aria-label="Direct link to Read the initial database service view" title="Direct link to Read the initial database service view" translate="no">​</a></h2>
<p>Open <strong>Database</strong> after signing in to the verified SSH endpoint. Check whether the SQL Server unit exists and read its current state.</p>
<p>Where available, note memory, CPU time and service uptime. Unavailable metrics should remain N/A. These fields describe the Linux service and accounting interfaces; they are not a complete picture of query workload, transaction health or database recovery.</p>
<p>Record the sample time. If the page reports a connection problem, resolve that before interpreting the visible service state as a current reading from Ubuntu.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="confirm-that-the-account-may-perform-the-action">Confirm that the account may perform the action<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#confirm-that-the-account-may-perform-the-action" class="hash-link" aria-label="Direct link to Confirm that the account may perform the action" title="Direct link to Confirm that the account may perform the action" translate="no">​</a></h2>
<p>The restart uses the registered SSH account's existing sudo permissions. Logging in successfully does not automatically authorize changing a database service.</p>
<p>If the command is denied, capture the sanitized result and involve the server owner. Do not substitute a broader account or change policy without an explicit administrative decision.</p>
<p>A permitted service operation is still subject to maintenance ownership. Review access and recovery arrangements before the planned window so that a permission problem does not create pressure to make an unreviewed change during downtime.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-the-impact-warning">Read the impact warning<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#read-the-impact-warning" class="hash-link" aria-label="Direct link to Read the impact warning" title="Direct link to Read the impact warning" translate="no">​</a></h2>
<p>Choose <strong>Restart SQL Server</strong> only when the intended database service is the correct target. Read the warning about dependent applications and confirm when the maintenance window is ready.</p>
<p>During a lab exercise, cancel a confirmation first and verify that no restart occurred. This makes the cancellation path familiar before the actual operation.</p>
<p>When confirming the real test, submit once and wait. The dashboard prevents conflicting operations through its coordinator and reports the command result. Repeated clicks or requests from other tabs do not make database recovery complete sooner.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="interpret-the-command-result-narrowly">Interpret the command result narrowly<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#interpret-the-command-result-narrowly" class="hash-link" aria-label="Direct link to Interpret the command result narrowly" title="Direct link to Interpret the command result narrowly" translate="no">​</a></h2>
<p>A successful restart command is evidence about the service management operation. It does not establish that every database is online, that all application connections recovered, or that every dependent job resumed.</p>
<p>If the operation fails, read the actual error and current service state. Differentiate permission denial, a command failure and a client timeout. Those conditions suggest different follow-up work.</p>
<p>The <a href="https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-troubleshooting-guide?view=sql-server-ver17" target="_blank" rel="noopener noreferrer" class="">Microsoft SQL Server Linux troubleshooting guide</a> provides database-operator diagnostics. Use its version-appropriate guidance for the installation instead of treating the dashboard's service status as a complete recovery report.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="verify-database-readiness-separately">Verify database readiness separately<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#verify-database-readiness-separately" class="hash-link" aria-label="Direct link to Verify database readiness separately" title="Direct link to Verify database readiness separately" translate="no">​</a></h2>
<p>After the service operation, the authorized database operator should perform the team's established readiness check. That check may involve a known connection and a small read-only query through existing tools.</p>
<p>Keep that activity outside the dashboard's service-management claim. The app does not acquire application database credentials or issue readiness queries on your behalf.</p>
<p>Record the actual result and time. A process can exist before a particular database is ready for the application's use. Allow the expected recovery procedure to complete before declaring the maintenance successful or deciding a new restart is required.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="check-each-dependent-application">Check each dependent application<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#check-each-dependent-application" class="hash-link" aria-label="Direct link to Check each dependent application" title="Direct link to Check each dependent application" translate="no">​</a></h2>
<p>Use Website Health for appropriate public endpoints, then verify a representative application function through its approved operational check.</p>
<p>A homepage that does not access SQL Server may answer while a database-backed feature still fails. A protected endpoint can intentionally return an authentication response. Choose checks whose expected behavior you understand.</p>
<p>For workers, use their own read-only operational signals. A running process is not proof that its last job completed. Keep the test tied to the dependent function that the maintenance could have interrupted.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="investigate-a-timeout-before-retrying">Investigate a timeout before retrying<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#investigate-a-timeout-before-retrying" class="hash-link" aria-label="Direct link to Investigate a timeout before retrying" title="Direct link to Investigate a timeout before retrying" translate="no">​</a></h2>
<p>A bounded client request can time out while a remote systemd job continues. Inspect the current unit state and relevant operator diagnostics before submitting another restart.</p>
<p>Record the time and result of the first request. Check whether the service is still transitioning or whether database recovery is progressing under the existing process.</p>
<p>If the evidence remains unclear, hand the case to the database owner with the observed state and sanitized error. Repeating a restart can interrupt recovery and make the sequence harder to understand. The next action should follow a new decision based on current evidence.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="keep-the-maintenance-record-precise">Keep the maintenance record precise<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#keep-the-maintenance-record-precise" class="hash-link" aria-label="Direct link to Keep the maintenance record precise" title="Direct link to Keep the maintenance record precise" translate="no">​</a></h2>
<p>Open Audit History and verify the recorded target, action, account, timestamp and result. The dashboard's audit entry is a local record of the management workflow.</p>
<p>Add the separate database and dependent-application checks to the team's maintenance note. This connects the service action to the actual outcome users care about.</p>
<p>Protect the note and any log excerpts appropriately. A public issue needs only the minimum details required to reproduce a product defect. Connection strings, credentials, private database names and complete error logs often exceed that need.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="plan-rollback-and-escalation-before-the-window">Plan rollback and escalation before the window<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#plan-rollback-and-escalation-before-the-window" class="hash-link" aria-label="Direct link to Plan rollback and escalation before the window" title="Direct link to Plan rollback and escalation before the window" translate="no">​</a></h2>
<p>A restart does not itself supply a database rollback mechanism. The database owner's recovery plan should already define what to do if the service cannot start or a dependent application fails after maintenance.</p>
<p>Identify who can inspect database-level diagnostics and who can approve further action. Record when the team should stop an exercise and restore the known lab state.</p>
<p>This preparation keeps the dashboard in its intended role: a clear, bounded way to request a known service operation and inspect its result. The broader recovery decision stays with the responsible operators.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="complete-the-exercise-with-all-three-outcomes">Complete the exercise with all three outcomes<a href="https://serverappmanager.ommrudraksha.com/blog/safely-restart-sql-server-ubuntu/#complete-the-exercise-with-all-three-outcomes" class="hash-link" aria-label="Direct link to Complete the exercise with all three outcomes" title="Direct link to Complete the exercise with all three outcomes" translate="no">​</a></h2>
<p>A successful lab record covers the Linux service operation, database readiness and dependent application recovery separately. It includes a cancelled confirmation and a failure or denied-permission scenario if those are part of the evaluation.</p>
<p>Do not compress a partially completed recovery into a single success label. State which checks passed and which remain pending.</p>
<p>Read the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/sql-server/">SQL Server guide</a>, <a class="" href="https://serverappmanager.ommrudraksha.com/docs/audit-history/">audit guide</a> and <a href="https://github.com/OmmLabs/MyServerManager/blob/main/SECURITY.md" target="_blank" rel="noopener noreferrer" class="">application security notes</a> for the current dashboard scope and operational boundaries.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label="Operations" term="Operations"/>
        <category label="systemd" term="systemd"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Verify an Ubuntu SSH host key before signing in]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/"/>
        <updated>2026-11-21T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Compare the server's independently trusted SSH fingerprint before sending your password, and handle a changed key carefully.]]></summary>
        <content type="html"><![CDATA[<p>An SSH address tells an application where to connect. The host key helps it check which server answered. Before you type an Ubuntu password into Server App Manager, the first-run screen asks you to verify that host identity.</p>
<p>This guide explains that decision using a sample endpoint. It covers the dashboard's current password-based source preview and the information to request from a server administrator. It does not ask you to change an SSH service or accept an unexplained key.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="separate-the-credentials-you-are-looking-at">Separate the credentials you are looking at<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#separate-the-credentials-you-are-looking-at" class="hash-link" aria-label="Direct link to Separate the credentials you are looking at" title="Direct link to Separate the credentials you are looking at" translate="no">​</a></h2>
<p>Three things can appear in an SSH discussion: the account password, a user's login key and the server's host key. They serve different purposes.</p>
<p>The password is a credential for the Ubuntu account. A user's SSH login key pair is another possible account authentication method. A server host key belongs to the endpoint answering the connection and is used when checking that endpoint's identity.</p>
<p>A fingerprint is a compact representation of a key. It is useful for comparison, but a displayed fingerprint does not establish trust on its own. You still need a trusted expected value for the intended machine. The first connection is where that independent information matters most.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="obtain-the-expected-fingerprint-first">Obtain the expected fingerprint first<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#obtain-the-expected-fingerprint-first" class="hash-link" aria-label="Direct link to Obtain the expected fingerprint first" title="Direct link to Obtain the expected fingerprint first" translate="no">​</a></h2>
<p>Ask the server owner for the host-key type and SHA-256 fingerprint through a channel you already trust. A hosting-provider console or an established administrator contact can provide that reference.</p>
<p>Confirm which environment the information describes. An organization can have a test VM, production VM and replacement VM behind similar names. Record the intended hostname and SSH port alongside the fingerprint so that the reference is connected to a particular endpoint.</p>
<p>Do not use a screenshot sent by an unknown contact as your only authority. Likewise, retrieving a key over the same unverified network path only tells you what that path currently presents. It does not independently establish that the responder is the server you intend to manage.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="inspect-a-public-host-key-from-a-trusted-console">Inspect a public host key from a trusted console<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#inspect-a-public-host-key-from-a-trusted-console" class="hash-link" aria-label="Direct link to Inspect a public host key from a trusted console" title="Direct link to Inspect a public host key from a trusted console" translate="no">​</a></h2>
<p>An authorized administrator can inspect the public host-key file for the algorithm involved. For an Ed25519 host key, a typical read-only command is:</p>
<div class="language-sh codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#bfc7d5;--prism-background-color:#292d3e"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-sh codeBlock_bY9V thin-scrollbar" style="color:#bfc7d5;background-color:#292d3e"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#bfc7d5"><span class="token plain">ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub</span><br></div></code></pre></div></div>
<p>This reads a public key file and displays its fingerprint. The path is an example for that key type; use the actual public host-key file on the intended machine. Keep this console access independent of the unverified connection you are checking.</p>
<p>The <a href="https://man.openbsd.org/ssh-keygen.1" target="_blank" rel="noopener noreferrer" class="">OpenSSH ssh-keygen manual</a> documents fingerprint display and hash selection. You do not need to generate a new key to inspect an existing public key's fingerprint. Avoid exposing or copying the server's private host-key file during this task.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="match-the-key-type-as-well-as-the-value">Match the key type as well as the value<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#match-the-key-type-as-well-as-the-value" class="hash-link" aria-label="Direct link to Match the key type as well as the value" title="Direct link to Match the key type as well as the value" translate="no">​</a></h2>
<p>A server can have more than one host key. A fingerprint for an RSA key will not match a fingerprint for an Ed25519 key, even when both keys belong to the same machine.</p>
<p>Read the type shown by the dashboard, then compare it with the trusted reference for that type. If your administrator supplied only another algorithm, ask for the corresponding reference rather than deciding that the mismatch is harmless.</p>
<p>Check the complete SHA-256 value. Comparing only the first few characters creates unnecessary ambiguity. If you are moving the reference between systems, watch for line wrapping, truncation and accidental spaces introduced by a message or screenshot.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="enter-the-same-endpoint-you-verified">Enter the same endpoint you verified<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#enter-the-same-endpoint-you-verified" class="hash-link" aria-label="Direct link to Enter the same endpoint you verified" title="Direct link to Enter the same endpoint you verified" translate="no">​</a></h2>
<p>In the dashboard, enter a value such as <code>user@server.example.com</code>. For an existing custom SSH port, use the dashboard's documented <code>user@server.example.com:2222</code> format.</p>
<p>Confirm all three endpoint components: username, host and port. A website's HTTPS port and an ASP.NET application's internal listening port are not automatically SSH ports.</p>
<p>The username selects the Ubuntu account, while the host key identifies the answering SSH endpoint. You can therefore get a correct host fingerprint and still enter an incorrect account name. Treat these as distinct checks when diagnosing an unsuccessful sign-in.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="read-the-first-run-confirmation-carefully">Read the first-run confirmation carefully<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#read-the-first-run-confirmation-carefully" class="hash-link" aria-label="Direct link to Read the first-run confirmation carefully" title="Direct link to Read the first-run confirmation carefully" translate="no">​</a></h2>
<p>The source preview first obtains the host identity without attempting password authentication. After you confirm the fingerprint, it verifies the confirmed key again during the password connection.</p>
<p>If the reference matches completely, confirm the trust step and then enter the account password. A successful first sign-in saves the registration locally. If authentication fails, that failure is about account access or policy; it should not be “fixed” by weakening host verification.</p>
<p>Use the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/connection/">connection guide</a> for the current screen flow. Product behavior can change between source revisions, so include the application revision when reporting a trust-screen problem.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="understand-what-gets-remembered">Understand what gets remembered<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#understand-what-gets-remembered" class="hash-link" aria-label="Direct link to Understand what gets remembered" title="Direct link to Understand what gets remembered" translate="no">​</a></h2>
<p>Server App Manager keeps the saved server profile in local state. Later sign-ins check the saved key rather than silently replacing it with whatever a connection presents.</p>
<p>This local profile is separate from the host records maintained by Windows OpenSSH. Trusting an endpoint in one client does not mean every other client has adopted that decision.</p>
<p>When comparing a terminal test with the dashboard, identify which trust record each one uses. The <a href="https://man.openbsd.org/ssh_config.5" target="_blank" rel="noopener noreferrer" class="">OpenSSH client configuration manual</a> describes its own host-key checking behavior and known-hosts settings. Those settings should not be assumed to control the dashboard's SSH implementation.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="investigate-a-changed-key-before-entering-credentials">Investigate a changed key before entering credentials<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#investigate-a-changed-key-before-entering-credentials" class="hash-link" aria-label="Direct link to Investigate a changed key before entering credentials" title="Direct link to Investigate a changed key before entering credentials" translate="no">​</a></h2>
<p>A key can legitimately change after a machine rebuild or a planned host-key rotation. A hostname can also resolve to another host, an address can be reassigned, or a connection can reach the wrong endpoint.</p>
<p>The visible mismatch alone does not distinguish those causes. Stop the sign-in attempt and ask the server owner to confirm what changed. Obtain the replacement fingerprint through the trusted channel again.</p>
<p>Record the old endpoint, expected environment, time of the change and verified new identity. This gives the next operator a clear explanation instead of a vague note that a warning was ignored during an incident.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="keep-recovery-separate-from-guessing">Keep recovery separate from guessing<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#keep-recovery-separate-from-guessing" class="hash-link" aria-label="Direct link to Keep recovery separate from guessing" title="Direct link to Keep recovery separate from guessing" translate="no">​</a></h2>
<p>If a saved registration must be replaced, follow the dashboard's documented removal and recovery process. Normal server removal requires a signed-in administrator and confirmation.</p>
<p>For a permanently unreachable saved server, the source guide describes a stopped-app procedure involving the local server profile. Use that procedure only after identifying the correct state directory and protecting the existing records.</p>
<p>Removing a saved profile changes what the local app remembers; it does not prove that a newly presented key is valid. You still need to verify the new host before reenrolling it. Read <a class="" href="https://serverappmanager.ommrudraksha.com/docs/update-and-remove/">update and removal</a> for the actual paths and current behavior.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="practice-a-mismatch-in-an-isolated-environment">Practice a mismatch in an isolated environment<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#practice-a-mismatch-in-an-isolated-environment" class="hash-link" aria-label="Direct link to Practice a mismatch in an isolated environment" title="Direct link to Practice a mismatch in an isolated environment" translate="no">​</a></h2>
<p>A useful lab exercise uses two disposable endpoints with different host keys and a clearly labeled test address. Enroll one verified identity, then present the other only within that controlled exercise.</p>
<p>The expected outcome is a blocked later sign-in, followed by investigation and independently verified reenrollment. Keep a record of what the app displayed and whether it prevented the credential step.</p>
<p>Label screenshots as lab examples and remove account names and addresses that identify real infrastructure. The purpose is to understand the trust workflow, not to collect a reusable bypass for a production warning.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="ask-for-the-right-help-when-something-fails">Ask for the right help when something fails<a href="https://serverappmanager.ommrudraksha.com/blog/verify-ubuntu-ssh-host-key-fingerprint/#ask-for-the-right-help-when-something-fails" class="hash-link" aria-label="Direct link to Ask for the right help when something fails" title="Direct link to Ask for the right help when something fails" translate="no">​</a></h2>
<p>A productive report includes the application revision, the key type displayed, whether this is first enrollment or a later sign-in, and the point at which the flow stopped.</p>
<p>You usually do not need to publish your real host address or a full authentication transcript to explain the interface problem. If a suspected vulnerability involves credentials or trust handling, use the <a class="" href="https://serverappmanager.ommrudraksha.com/security/">security reporting route</a> first.</p>
<p>A good result is simple to describe: the saved identity corresponds to the intended host, the comparison used an independent reference, and later identity changes stop for investigation. That gives the password sign-in step a clear foundation rather than relying on familiarity with an address.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label="SSH" term="SSH"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Introducing the Server App Manager source preview]]></title>
        <id>https://serverappmanager.ommrudraksha.com/blog/source-preview/</id>
        <link href="https://serverappmanager.ommrudraksha.com/blog/source-preview/"/>
        <updated>2026-11-09T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Explore the dashboard that uses your existing Ubuntu SSH connection and follow the local source quickstart.]]></summary>
        <content type="html"><![CDATA[<p>Server App Manager brings Ubuntu application status, logs and website checks into a dashboard on your PC. The source preview gives developers a way to try the local setup and review how it works.</p>
<p>Start with the <a class="" href="https://serverappmanager.ommrudraksha.com/docs/quickstart/">Windows quickstart</a>. You will verify a server fingerprint, sign in with your existing SSH account and review a service before adding it to the dashboard.</p>
<p>The project blog will cover practical tasks such as finding your ASP.NET Core service, reading its journal, checking cgroup memory and diagnosing Nginx errors. The <a class="" href="https://serverappmanager.ommrudraksha.com/docs/compatibility/">compatibility page</a> explains the preview's prerequisites. <a class="" href="https://serverappmanager.ommrudraksha.com/community/">Community</a> explains how to share a reproducible issue.</p>]]></content>
        <author>
            <name>Server App Manager team</name>
            <uri>https://github.com/OmmLabs</uri>
        </author>
        <category label="Project news" term="Project news"/>
    </entry>
</feed>