No PPPoE Configurations Were Found: How to Fix It

To get rid of “No PPPoE configurations were found,” create or restore the PPPoE connection your router or network device expects, then check that the modem, cabling, and ISP account support PPPoE. The message usually means the device has no usable PPPoE profile; it does not by itself prove that your internet service is down or that your password is wrong.

What the message means

PPPoE stands for Point-to-Point Protocol over Ethernet. It is a method some internet providers use to authenticate a subscriber and establish an internet connection over an Ethernet-based access network. A router configured for PPPoE needs a connection profile containing the service’s required settings, commonly a username and password.

The exact wording is not universal. It may appear in a router’s setup page, a network-management application, or another device’s interface. In each case, “no configurations were found” generally indicates that the software cannot find a PPPoE profile to use. It may be missing, not saved, attached to the wrong interface, or unavailable because the device is in a different operating mode.

Do not assume every internet connection uses PPPoE. Providers may instead use automatic IP addressing, often labelled DHCP, or a fixed IP configuration. Selecting PPPoE when the provider expects another connection type will not solve the problem.

Before changing settings

Confirm which device displays the message and how your service is connected. If you use a separate modem or optical network terminal (ONT) with a router, the ISP may expect the login on the router, on the modem/ONT, or on neither. The provider’s installation instructions or support team can confirm which device should handle the connection.

• Check the service plan or ISP documentation for the required connection type: PPPoE, DHCP, or static IP.
• Find the PPPoE username and password in the ISP’s account information or installation records. These may differ from your Wi-Fi name and Wi-Fi password.
• Record any existing router settings before editing them. Avoid a factory reset unless you know how to restore the ISP settings and other network configuration.
• Check that the Ethernet cable runs from the modem or ONT to the router’s designated WAN or Internet port, if your setup uses separate devices.

Set up or restore a PPPoE profile

Menu names differ by device, but the general process is similar. Use the router’s local administration page or official management app, and look for Internet, WAN, Broadband, or Connection settings. If the setup wizard offers connection types, select PPPoE only after confirming that this is what your ISP requires.

1. Open the Internet or WAN connection settings.
2. Choose PPPoE as the WAN connection type.
3. Enter the ISP-provided PPPoE username and password exactly as supplied. Check capitalization and any punctuation; do not substitute Wi-Fi credentials.
4. Leave optional fields, such as a service name or VLAN setting, unchanged unless the ISP specifically provides values for them.
5. Save or apply the settings, then allow the device time to reconnect. Check its connection status or event log for a successful session.

If the profile was present before, first check whether it is disabled, unsaved, or assigned to another WAN interface. Some devices support multiple internet connections, so a profile associated with a backup interface may not be used for the active connection. Consult the device’s own instructions rather than guessing at advanced fields.

Check the modem, cabling, and connection mode

A correctly entered profile cannot establish service if the physical link or upstream equipment is unavailable. Make sure the modem or ONT has power and that its status lights indicate a connection according to its documentation. Reseat the Ethernet cable at both ends, and try another known-good cable if available. Restarting the modem/ONT and router can help after a temporary interruption; follow the ISP’s recommended restart order and allow each device to finish booting.

Also check for a double-router setup. If an ISP gateway already establishes the PPPoE session and provides a local network, a second router may need to use DHCP on its WAN side, or be placed in access-point mode. Configuring PPPoE on both devices can prevent a connection or create other network problems. Conversely, if the gateway is only a bridge, the downstream router may need the PPPoE credentials.

Some providers require additional settings, such as a VLAN identifier, but these are not universal. Do not copy values from an unrelated router guide: incorrect provider-specific settings can prevent connection. Ask the ISP for the exact values and for confirmation about which device should perform PPPoE authentication.

Common causes and what to try next

• No profile was saved: Re-enter the WAN settings and use the page’s Save or Apply control. Confirm that the profile remains after leaving and reopening the settings page.
• Wrong connection type: Verify whether the ISP uses PPPoE or DHCP. If it uses DHCP, select the appropriate automatic-IP option instead of creating a PPPoE profile.
• Credentials are incorrect or incomplete: Request confirmation from the ISP. Some providers use a specific account format; do not add a suffix or change the username unless instructed.
• Wrong port or inactive upstream link: Verify the WAN cable path and inspect the modem/ONT status. A PPPoE profile cannot compensate for a disconnected service link.
• Settings were lost after a reset or update: Restore the ISP’s documented configuration and any required additional settings. Do not rely on generic defaults.
• Device software or interface issue: Sign out and back in, refresh the management page, or check for a documented firmware update. Avoid interrupting a firmware update once it starts.

If the profile exists but the router reports authentication failure, that is a different clue from “no configurations found.” Authentication failures point toward credentials or account provisioning; a missing-profile message points first toward configuration or interface selection. A link-down or timeout status may instead indicate cabling, upstream service, or provider equipment.

When to contact your ISP

Contact the ISP if you cannot confirm the correct connection type, do not have the PPPoE credentials, or need provider-specific VLAN or service settings. Ask whether the modem/ONT is bridged, whether a router should make the PPPoE connection, and whether the service is active. If the ISP confirms the settings and the router still cannot find or use a profile, contact the router manufacturer or administrator responsible for the device.

When requesting help, provide the device model, the exact message, the connection layout, and any status shown for the WAN link or PPPoE session. Do not post account credentials publicly or send them through an unverified channel.

Frequently Asked Questions

Is “No PPPoE configurations were found” an ISP outage?
Not necessarily. It most directly indicates that the device cannot find a usable PPPoE profile. A service outage is possible, but check the configuration and connection status before concluding that the provider is down.

Where do I get my PPPoE username and password?
Check your ISP’s setup documents or account portal, or contact the provider. These credentials are separate from the Wi-Fi name and password unless the ISP explicitly says otherwise.

Should I choose PPPoE or DHCP?
Use the connection type specified by your ISP. PPPoE requires an authentication profile; DHCP generally obtains network settings automatically without PPPoE credentials.

Will restarting the router fix the message?
A restart may clear a temporary interface or connection problem, but it will not create a missing profile or correct the wrong connection type. Check and save the WAN settings first.

Will a factory reset remove the error?
It may clear corrupted settings, but it also erases the router’s configuration and may leave you without internet until you restore all required settings. Use it only when necessary and when you have the setup details.

Related

• Neural Networks: What Did They Just Hack?
• Copilot and OneDrive: What You Can Do
• LiteLLM: How a CI Scanner Led to Malicious PyPI Releases