Unable to access localhosted zammad on windows system on same network

Infos:

  • Used Zammad version: 6.3.1
  • Used Zammad installation type: ,package
  • Operating system: Ubuntu 24.04
  • Browser + version: Firefox and Chrome

Expected behavior:

Access localhosted zammad through ip on other systems.

Actual behavior:

Unable to access localhosted zammad (installed on Ubuntu 24.04) on windows system on same network

@MrGeneration
Can you help me with this issue?

Need more information to help you here.

How are you trying access Zammad?

Are you using FQDN or IP?

Are you getting an error?

Difficult to help with such limited information.

1 Like

Hey Sal,

I have localhosted zammad(Ubuntu 24.04) in our company premises
And i am trying to get acces in company network

While i am able to connect to zammad web in localhosted system
But when i am trying to connect in other system like windows machine it show “This site can’t be reached” error

Are your ports open on your Linux machine? Are you using standard web ports? If it standard ports the do a port scan from your windows machine.

nmap

this should scan the most common ports.

Hi Ak
Ports 80 and 443 are open on my machine.

Are you using a proxies or are you on a different subnet?

You say port 443 and 80 is open but does that show up on your other machines when you scan for ports of the zammad computer?

You can access Zammad from the same machine it’s installed on, and everything works? This sounds like a Network issue, not a Zammad issue.

But any other system, and you get an error “The site can’t be reached” I’m assuming this is the DNS error?

Check to make sure Ubuntu isn’t blocking traffic to ports 80/443.

Are you using the IP address from the other machine as well?

For example, let’s say Zammad is on 10.25.1.100 and your other machine is on 10.25.1.101.

When you are on 101 you get that error? That’s a network error and 101 is unable to see 100. Especially if you are using the IP address instead of FQDN.

As @AK2024 mentioned, are you behind a proxy?
What is your firewall (Palo Alto, Fortinet, OpenSense…). What NAT do you have in place, or any other routing that could impact this.

Can 101 ping 100?

We should start focussing on what error message you’re seeing in the browser and what exactly you’re trying how. The provided information is super thin and feels very dodgy.

If it’s an internal service any way (so internal IPs for example), it wouldn’t be an issue to share how you’re trying to access is (as in trying to connect to https://172.16.16.1 as example).

Right now it’s super hard to help you at all. Sal is doing their best but is more digging in the dark due to that.

1 Like

Hi @MrGeneration

Please find attached images.
As i am able to access Zammad on same system while using Localhost and if i am trying to access using ip it show this error tried ports 80,81,443 and 3000.







Well your virtual host obviously is set up to react on ‘localhost’.
You’ll have to set up DNS records, ssl certificates and adjust your virtual host accordingly.

We have a section about that in our documentation:
https://docs.zammad.org/en/latest/getting-started/configure-webserver.html

It won’t be able to explain everything in finest detail though.