F5F Stay Refreshed Software Operating Systems Ubuntu was set up through IPMI but the remote machine is unable to reach the internet.

Ubuntu was set up through IPMI but the remote machine is unable to reach the internet.

Ubuntu was set up through IPMI but the remote machine is unable to reach the internet.

Pages (2): 1 2 Next
A
Angu197
Member
151
06-26-2025, 12:54 PM
#1
You need to install Ubuntu 22 manually on the unmanaged server. Since it's an unmanaged system, you can use the IPMI management panel to perform the installation. Make sure you have the correct network settings and access credentials. Follow the official Ubuntu installation guide for unmanaged systems.
A
Angu197
06-26-2025, 12:54 PM #1

You need to install Ubuntu 22 manually on the unmanaged server. Since it's an unmanaged system, you can use the IPMI management panel to perform the installation. Make sure you have the correct network settings and access credentials. Follow the official Ubuntu installation guide for unmanaged systems.

C
cHiMiRaTa
Member
80
06-26-2025, 05:01 PM
#2
I've faced similar issues with poor service providers—probably the same one you mentioned, starting with a 'v' in its name. Restarting your OS shouldn't alter any network settings. Verify the IP configuration; if it shows an assigned IP and routes, that's likely the provider's issue.
C
cHiMiRaTa
06-26-2025, 05:01 PM #2

I've faced similar issues with poor service providers—probably the same one you mentioned, starting with a 'v' in its name. Restarting your OS shouldn't alter any network settings. Verify the IP configuration; if it shows an assigned IP and routes, that's likely the provider's issue.

G
Giorikas_19
Member
56
06-26-2025, 06:04 PM
#3
Can you revert to the standard setup? You’ll probably have to record the default gateway’s IP and any DNS servers, ensuring your manual setup aligns with them. The server’s own IP might also matter. No special steps during installation are required—just confirm it can reach the internet by setting the right gateway. Ideally, a DHCP server would provide these details, but it seems you’ll need to handle this yourself.
G
Giorikas_19
06-26-2025, 06:04 PM #3

Can you revert to the standard setup? You’ll probably have to record the default gateway’s IP and any DNS servers, ensuring your manual setup aligns with them. The server’s own IP might also matter. No special steps during installation are required—just confirm it can reach the internet by setting the right gateway. Ideally, a DHCP server would provide these details, but it seems you’ll need to handle this yourself.

S
SumoStriker82
Junior Member
2
06-26-2025, 10:19 PM
#4
Yes, it should be a local IP address. You only have the public IP available at the moment.
S
SumoStriker82
06-26-2025, 10:19 PM #4

Yes, it should be a local IP address. You only have the public IP available at the moment.

K
KateKitKat
Member
138
07-13-2025, 04:58 PM
#5
The IP should be public. Have you verified the routes and tried a traceroute? I use 1.1.1.1 or 8.8.8.8 because they’re simple to recall.
K
KateKitKat
07-13-2025, 04:58 PM #5

The IP should be public. Have you verified the routes and tried a traceroute? I use 1.1.1.1 or 8.8.8.8 because they’re simple to recall.

J
JayBee757
Member
142
07-14-2025, 12:09 PM
#6
DHCP isn't assigning me an IP address. I contacted CS for network information. Awaiting their response.
J
JayBee757
07-14-2025, 12:09 PM #6

DHCP isn't assigning me an IP address. I contacted CS for network information. Awaiting their response.

S
SquishyJelly3
Member
181
07-14-2025, 01:32 PM
#7
Not always. I've experienced cases where the physical server had a private IP, and the VM's public IP wasn't assigned directly. Without using that specific IP, the connection would fail.
S
SquishyJelly3
07-14-2025, 01:32 PM #7

Not always. I've experienced cases where the physical server had a private IP, and the VM's public IP wasn't assigned directly. Without using that specific IP, the connection would fail.

T
TiemDiamond
Member
114
07-25-2025, 10:59 AM
#8
Failed to start traceroute due to network connectivity issues.
T
TiemDiamond
07-25-2025, 10:59 AM #8

Failed to start traceroute due to network connectivity issues.

M
MrJoris02
Member
195
08-09-2025, 11:10 PM
#9
No, it displays available routes without showing a default gateway.
M
MrJoris02
08-09-2025, 11:10 PM #9

No, it displays available routes without showing a default gateway.

T
TdmFan92
Senior Member
602
08-10-2025, 06:53 AM
#10
Usually this applies only to PaaS or IaaS environments. Common budget OpenVZ or KVM VPS setups come with public IP addresses built in. I've never encountered that before. PaaS and IaaS typically include virtualized dedicated firewalls.
T
TdmFan92
08-10-2025, 06:53 AM #10

Usually this applies only to PaaS or IaaS environments. Common budget OpenVZ or KVM VPS setups come with public IP addresses built in. I've never encountered that before. PaaS and IaaS typically include virtualized dedicated firewalls.

Pages (2): 1 2 Next