Jump to content

Webadmin: Failed to create virtual server : A virtual server with the same name and port already exists


dil_bert

Recommended Posts

hello dear fellows 

 

currently struggle with Webadmin:  after creating a new vhost i get this error message


Failed to create virtual server : A virtual server with the same name and port already exists

 

but believe it or not - in the list of vhosts it does not appear. 

 

how to go on  - what to do? 

 

Any idea !? 

Link to comment
Share on other sites

hello dear requinix many thanks for the quick reply.

i am really happy to hear from you.  Youre right!! Sure  thing!

but believe it or not - in the list of the allready existing  vhosts it does not appear. 

 

how to go on  - what to do? 

Link to comment
Share on other sites

first of all - i  will update the webmin-tool 
 
 
will have a closer look if i get rid of this behaviour
 
 
found  two great documentations - here
 
 
the howTo on digitalocean is very clear and concise: 
 
see the steps the guys suggest to do in this set  up: 

Prerequisites

Step One — Create the Directory Structure

Quote

The first step that we are going to take is to make a directory structure that will hold the site data that we will be serving to visitors.

Step Two — Grant Permissions

Quote
Quote

 

Now we have the directory structure for our files, but they are owned by our root user. If we want our regular user to be able to modify files in our web directories, we can change the ownership by doing this:
sudo chown -R $USER:$USER /var/www/example.com/public_html
sudo chown -R $USER:$USER /var/www/test.com/public_html
The $USER variable will take the value of the user you are currently logged in as when you press Enter. By doing this, our regular user now owns the public_html subdirectories where we will be storing our content.


Step Three — Create Demo Pages for Each Virtual Host
 

Quote

 

We have our directory structure in place. Let's create some content to serve.

We're just going for a demonstration, so our pages will be very simple. We're just going to make an index.html page for each site.

Let's start with example.com. We can open up an index.html file in our editor by typing:

nano /var/www/example.com/public_html/index.html
In this file, create a simple HTML document that indicates the site it is connected to. My file looks like this:

/var/www/example.com/public_html/index.html
<html>
  <head>
    <title>Welcome to Example.com!</title>
  </head>
  <body>
    <h1>Success!  The example.com virtual host is working!</h1>
  </body>
</html>

 

 

Step Four — Create New Virtual Host Files

Step Five — Enable the New Virtual Host Files

Quote

Now that we have created our virtual host files, we must enable them. Apache includes some tools that allow us to do this.
We can use the a2ensite tool to enable each of our sites like this

:
Step Six — Set Up Local Hosts File (Optional)


Step Seven — Test your Results

Quote


Now that you have your virtual hosts configured, you can test your setup easily by going to the domains that you configured in your web browser:

 

end of the citation of digitalocean - the great howTo : https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-ubuntu-16-04

 

well i will follow these steps and will have a closer look at the results... 

 

will come back and report all the findings 

 

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.