--- title: "Troubleshooting Using the Local Web Server" slug: "troubleshooting-using-the-local-web-server" description: "Learn how to use the Graphiant Edge local web server to diagnose connectivity and onboarding issues." updated: 2026-09-23T19:37:17Z published: 2026-09-23T19:37:17Z canonical: "docs.graphiant.com/troubleshooting-using-the-local-web-server" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.graphiant.com/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting Using the Local Web Server ## What is Graphiant’s Local Web Server? Graphiant’s Local Web Server provides you direct access to your Edge. The local web server is key in helping you: - Set the WAN configuration to get your Edge connected to the Graphiant Portal when DHCP is not available - Troubleshoot connection issues when not connected to the Graphiant Portal > [!NOTE] > This article covers troubleshooting connection issues. > > For information on onboarding your Edge, see [Onboarding Your Graphiant Edge Using the Local Web Server](https://docs.graphiant.com/docs/local-web-server). ## How Do I Locate Graphiant’s Local Web Server Ensure that you are connected to your Graphiant Edge through the last (local management) port. > [!NOTE] > Note: > > You must be on the same network as the local management interface. When your Edge comes up and doesn’t connect to the Portal, it will enable a DHCP server on its management interface to give you an IP address. > > As soon as the connection to the Graphiant Portal comes up, the Edge will disable that DHCP server but you can still access the management interface via https://192.168.1.1 by setting a static IP address on your laptop. > > On virtual Edges (i.e. KVM and ESXi), the DHCP server on the local management port is disabled by design, regardless of Portal connectivity state. To access the local web server on a virtual Edge, you must manually assign a static IP address in the `192.168.1.0/24` subnet (e.g., `192.168.1.2/24`) to the interface or virtual bridge connected to the Edge's management port, then browse to [https://192.168.1.1](https://192.168.1.1). The Graphiant Local Web Server is only reachable via your web browser. Point your browser to: [https://192.168.1.1](https://192.168.1.1) You will receive a security warning due to Graphiant using a Self-Signed Certificate; **accept to connect**. You will see the Graphiant Local Web Server Portal. Simply **click ‘Login’** to access your edge. > [!NOTE] > If your Graphiant Edge has previously been connected to the Graphiant Portal: > > You will need to enter the password you configured there. ![Login screen for a corporate network with a welcome message and password field.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Portal 'Login'.jpg) You will now be in the Graphiant Local Web Server for your Edge. ![Device configuration dashboard showing connectivity status and onboarding details for network devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Landing Dashboard.jpg) When troubleshooting, you will utilize these sections of the Local Web Server: - [**Dashboard**](/v1/docs/local-web-server#local-web-server-dashboard-summary)**:** Contains the configuration summary information for your Edge - [**Network Tools**](/v1/docs/local-web-server#network-tools)**:** Testing via ping, trace route, and throughput, in addition to ARP and DNS lookup - [**Diagnostics & Logs**](/v1/docs/local-web-server#diagnostics-logs)**:** Shows insight into logs for packet capture, support, device and reboot histories > [!NOTE] > ‘Reboot Device’ and ‘Logout’ are available at all times at the top of your screen. ![Device configuration dashboard showing connectivity status and onboarding details for network devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Landing Dashboard.jpg) ## Local Web Server Dashboard The landing page for the local web server is the Dashboard. This gives you all of the following: - [**Device Details**](/v1/docs/local-web-server#device-details) - [**Device Configuration**](/v1/docs/local-web-server#device-configuration) - [**Connectivity Diagram**](/v1/docs/local-web-server#connectivity-diagram) ### Device Details - **Platform** - **Graphiant Network Operating System Firmware Version** - **UUID** - **Serial Number** - **Hardware Serial** - **Onboarding State:** Where the Edge is within it’s onboarding process - **Onboarding Failure Reason:** Should an onboarding attempt have been made, the reason will appear here - **Onboarding URL:** If onboarded, this will show the address your Edge uses to connect to the Graphiant network - **Uptime:** The length of time the connection to the local web server has been active ### Device Configuration - **Hostname:** Reflects the name of your Edge that is assigned when connected to the Graphiant Portal; i - This field is uneditable - **DNS Settings:** Whether you are utilizing a Dynamic (DHCP) or Static DNS, or if you prefer to use Cloudflare - **If ‘Static’ is selected:** You will be asked to provide the primary and secondary IPv4/IPv6 addresses. From here, you can select to go directly to [configure your WAN circuits](/v1/docs/local-web-server#wan-circuits) without going tab by tab. ### Connectivity Diagram The connectivity of your device to the Graphiant Portal is shown here. > [!NOTE] > As this Edge is not yet onboarded: > > The Connectivity Diagram is not yet showing green to the Graphiant Portal. ![Device configuration dashboard showing connectivity status and onboarding details for network devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Landing pg 'Dashboard' tab underlined.jpg) ## Network Tools The network tools tab houses the troubleshooting methods: - [**Ping**](/v1/docs/local-web-server#ping)**:** Tests connectivity by sending packets to a target and measuring response time - [**Trace Route**](/v1/docs/local-web-server#trace-route)**:** Shows the hop-by-hop network path the packets take to reach a destination and their metrics - [**Throughput Test**](/v1/docs/local-web-server#throughput-test)**:** Measures data transmission speed - [**ARP**](/v1/docs/local-web-server#arp-address-resolution-protocol)**:** Displays IP-to-MAC address mappings to verify local device communication - [**DNS Lookup**](/v1/docs/local-web-server#dns-lookup)**:** Resolves a domain name to its IP address to confirm DNS is working correctly ![Network tools interface displaying ping test parameters and options for IP addresses.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Network Tools tab.jpg) ### Ping When you test connectivity using the Ping capability, you send packets to your target and measure the response time. ![Network tools interface displaying the Ping test parameters and options for testing.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Ping pg.jpg) Fill out the following fields: - **General:** - **LAN Segment / WAN Circuit:** Source of the ping - **Interface:** Specific interface used to send the ping packets - **Source IP:** IP address sending the ping request - **Destination IP:** IP address you’re testing connectivity to - **Protocol:** - If selecting ICMP, there are no more General fields after “Protocol” - If selecting TCP you will need to also fill out: - **Destination Port:** The TCP port number used for the connection test; the port must be open and available for a successful test - **Advanced (*Optional*):** - **Count:** Number of ping packets to send during the test (default = 5) - **Payload Size:** Amount of data contained in each ping packet (default = 64 bytes) **Click ‘Start Test’.** ![Network tools interface displaying ping test parameters and options for configuration.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Ping ICMP fields.jpg) The results will appear at the bottom of the page, and include: - **Ping:** Successful / Unsuccessful - **Max Ping:** Longest response time from all ping replies. - **Min Ping:** Shortest response time from all ping replies - **Avg Ping:** Average response time across all ping replies - **Loss:** Percentage of ping packets that did not receive a reply ![Network tools interface displaying ping test results and parameters for connectivity assessment.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Ping results.jpg) ### Trace Route When you test connectivity using the Trace Route capability, you are able view the hop-by-hop path your packets are taking, along with their metrics. Graphiant supports both: - **Trace Route** - A one-time snapshot view of the path your packets take from the source to the destination, listing each hop along the way and their latency - **Trace Route with MTR** - A repeated test (per your specified packet quantity) of the route that not only shows each hop, but also measures their latency and packet loss ![Network tools interface displaying trace route options and parameters for testing connectivity.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Trace Route pg.jpg) Fill out the following fields: - **General:** - **MTR:** - **Toggled Off:** Displays the one-time path and latency - **Toggled On:** Tests the route according to Poll Count per Hop, showing latency and packet loss per hop - **Poll Count per Hop:** Number of packets sent to each hop during the MTR test - **LAN Segment / WAN Circuit:** Source of the trace route - **Interface:** Specific interface used to send the trace route - **Source IP:** IP address initiating the trace route request - **Destination IP:** IP address you’re testing connectivity to - **Protocol:** - If selecting ICMP, there are no more General fields after “Protocol” - If selecting TCP you will need to also fill out: - **Destination Port:** The TCP port number used for the connection test; *the port must be open and available for a successful test* - **Advanced (*Optional*):** - **Payload Size:** Amount of data contained in each trace route packet (default = 64 bytes) **Click ‘Run Traceroute’.** ![Network tools interface displaying trace route parameters and options for testing connectivity.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Trace Route fields filled in; 'Run Traceroute'(1).jpg) #### Trace Route results (No MTR). The results will appear at the bottom of the page and include: - **Test Results**: - **Trace Path:** Successful / Failed - **Trace Path Stopped:** Last hop that responded before the path stopped and ended the trace - **Max Latency at:** Which hop experienced the highest delay - **Max Latency amount:** Longest response time recorded during the trace - **Trace Path Table:** - **DNS Name / IP Address:** Hostname and IP address of each hop along the route - **Round Trip Time:** Time for a packet to reach a hop and return ![Network tools interface displaying trace route parameters and test results summary.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Trace Route No MTR Results.jpg) #### Trace Route with MTR Results The results will appear at the bottom of the page and include: - **Test Results**: - **Trace Path:** Successful / Failed - **Trace Path Stopped:** Last hop that responded before the path stopped and ended the trace - **Max Latency at:** Which hop experienced the highest delay - **Max Latency amount:** Longest response time recorded during the trace - **Trace Path Table:** - **DNS Name / IP Address:** Hostname and IP address of each hop along the route - **Loss %:** Percentage of packets lost at each hop - **Sent:** Total number of probe packets sent to that hop - **Last:** Latency from the most recent probe packet - **Average:** Average round-trip time to that hop across all probes - **Best:** Shortest round-trip time recorded for that hop - **Worst:** Longest round-trip time recorded for that hop - **StDev (Standard Deviation):** How much the latency varies; higher values = less stable performance ![Network tools interface displaying trace route results and latency metrics for troubleshooting.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Trace Route MTR Results.jpg) ### Throughput Test When you test connectivity using the Throughput Test capability, you measure the speed of your data transmission. ![Network tools interface displaying the throughput test option and related parameters.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Throughput Test pg.jpg) Complete the following fields: - **WAN Circuit:** Network connection used to run the throughput test - **Service****:** Throughput test service provider - **Server:** Test endpoint that measures data transfer speed between your site and the network ![Network tools interface displaying throughput test parameters and options for testing.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Throughput Test fields filled in; 'Start Test'.png) The results will appear at the bottom of the page and include: - **Download:** Speed at which data is received from the test server - **Upload:** Speed at which data is sent to the test server - **Jitter:** Variation in packet delay; lower values = more stable connection - **Average Ping:** Average round-trip time for test packets between your site and the server - **Provider:** Name of the internet service provider (ISP) used for this test connection - **IP Address:** Public IP address detected for the test server - **Loca****tion:** Geographic location of the test server ![Throughput test results showing download and upload speeds with additional network parameters.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Throughput Test Results.png) ### ARP (Address Resolution Protocol) When you test connectivity using the ARP capability, you view IP-to-MAC address mappings to verify local device communication. ![Network tools interface displaying ARP settings and options for interface selection.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 ARP pg.jpg) **Select the interface** you want to use to check for IP-to-MAC address mapping. > [!NOTE] > The ARP test will run immediately when you select the interface. ![Network tools interface showing ARP options and interface selection dropdown menu.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 ARP field highlighted.png) The results will appear at the bottom of the page and include: - **IP Address:** Network address of the device - **MAC Address:** Physical hardware address linked to that corresponding IP ![ARP table displaying IP and MAC addresses for network neighbors.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 ARP Results.png) ### DNS Lookup When you test connectivity using the DNS Lookup capability, the domain name is resolved to its IP address to confirm DNS is working correctly. ![Interface displaying DNS Lookup tool with input field and navigation options.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 DNS Lookup pg.jpg) Type the hostname / website you want to look up. **Click ‘Search’.** ![DNS Lookup tool interface with search bar for querying domain information.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 DNS Lookup filled in; 'Search'.png) The results will appear at the bottom of the page and include: - **Address:** IP address resolved for the domain - **TTL (Time To Live):** Time in seconds the DNS record remains valid before refresh ![DNS lookup results for graphiant.com showing two IP addresses and TTL values.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 DNS Lookup Results.png) ## Diagnostics & Logs The Diagnostics & Logs tab provides access to the following data and histories for troubleshooting and analysis: - [**Connectivity Test:**](/v1/docs/troubleshooting-using-the-local-web-server#connectivity-test) Checks that your Edge can reach internal and external endpoints - [**Packet Capture**](/v1/docs/local-web-server#packet-capture)**:** Captures live network traffic on a selected interface to help analyze communication or troubleshoot issues - [**Support Archive**](/v1/docs/local-web-server#support-archive)**:** Gathers and bundles a comprehensive snapshot of a network device’s configuration and status for troubleshooting - [**Device Logs**](/v1/docs/local-web-server#device-logs)**:** Shows recorded activity for the device, including configuration or connection changes over time - [**Reboot History**](/v1/docs/local-web-server#reboot-history)**:** Displays a log of past device reboots, including timestamps and reasons when available. ![Connectivity test interface displaying various network diagnostic options and settings.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Diagnostics and Logs landing pg all carats closed.jpg) ### Connectivity Test The connectivity test verifies that your Edge can reach Graphiant services as well as external endpoints across all necessary network planes and protocols. ![Connectivity Test section displaying various network diagnostic options and settings.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Conn Test highlighted in sidebar.jpg) **Click the carat for Test Settings.** ![Connectivity test settings with various options for network diagnostics displayed on the screen.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Conn Test Open Carat for Test Settings.jpg) **Select the circuit that you wish to test.** > [!NOTE] > Note: > > By default: > > - isp-11 is assigned to the first WAN interface > - isp-12 is assigned to the second WAN interface ![Connectivity test interface showing circuit selection and various connectivity options available.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Conn Test Select Circuit.jpg) **Click ‘Run All Tests’.** ![Connectivity test interface showing various options and a button to run tests.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Conn Test 'Run All Tests.jpg) The specific test results will be shown under each test. ![Connectivity test results showing passed statuses for various protocols and IP addresses.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Connectivity Testing 1_enhanced.png) ### Packet Capture Packet Capture helps you analyze communication, and troubleshoot issues, by capturing live network traffic on a specific interface. ![Packet capture interface with parameters for source, destination, and duration settings.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Packet Capture pg(1).jpg) Complete the following fields: - **General**: - **WAN Circuit:** Location of the packet capture - **Interface:** Specific network interface on that circuit from which to capture packets - **Duration:** How long the capture will run before automatically stopping - **Max Packet Capture *(Optional)*:** Limit on the total number of packets to capture before ending the session - > [!NOTE] > Regarding‘Duration’ and ‘Max Packet Capture’ values: > > Whichever value is hit first will be the deciding end of the session - **Filters (*Optional*):** - > [!NOTE] > Any, all, or no filters can be filled out depending on your needs. - **Source** - **IP Address or Prefix:** Captures only packets coming from this IP address or network range - **Port:** Captures only packets using this source port number - **Destination** - **IP Address or Prefix:** Captures only packets going to this IP address or network range - **Port:** Captures only packets using this destination port number - **DSCP:** Filters traffic to show only traffic with a specified DSCP value - **Protocol:** Limits capture to a specific protocol **Click ‘Start Capture’.** ![Packet capture settings including WAN circuit, interface, and duration parameters displayed on screen.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Packet Capture filled in; 'Start Capture'.jpg) The results will be in an exportable file. **Click ‘Export’.** ![Packet capture interface showing parameters and export option for network diagnostics.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Packet Capture Results; 'Export'.jpg) ### Support Archive Support Archive gives you a comprehensive snapshot of a network device’s configuration and status for troubleshooting, able to be utilized by our Support team. ![Support Archive section showing no data available at the moment.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Support Archive pg.jpg) **Click ‘Generate Archive’.** ![Support Archive interface showing no data available and option to generate archive.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Support Archive 'Generate Archive'.jpg) When finished, the status will show “Completed”, and give you the file name and timestamp. ![Support Archive showing completed status and timestamp for file generation.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Support Archive Completed.jpg) **Click ‘Download’** to have your Support Archive on file. ![Support archive details showing timestamp and file name for download.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Support Archive 'Download'.jpg) ### Device Logs Device Logs show configuration and connection changes over time in the recorded activity for the device. Information provided includes: - Timestamp - Severity level of event - Source (Originating System) - Message ![Device logs interface displaying search options and log records for network diagnostics.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Device Logs pg.jpg) You can search your Log Record using filters based on: - Date / Date Range - Severity of Event - Source (Originating system) - Message The filter will take effect immediately. ![Device logs interface showing search options and recent log entries for analysis.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS 2.0 Device Logs filters highlighted.jpg) ### Reboot History Reboot History shows timestamps and reasons (when available) of past device reboots. > [!NOTE] > Reboot History only logs manual Reboots upon clicking ‘Reboot’ in the header; > > Power-down / power-up, etc are not included here. ![Reboot history section displaying timestamp and reboot reason in network diagnostics interface.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/LWS Reboot History pg.jpg)