Topics Map > Services > Systems and Infrastructure for IT Partners > Web Publishing

Web Hosting - Connect to Pubweb

Below are instructions on how to connect to Pubweb.

Connection Settings 

Host name (server): pubweb.ndsu.nodak.edu 
Port: SFTP/SSH port 22 
Username: your NDSU Unix ID 
Password: your NDSU password 

Not sure what your Unix ID is? Log in to the pubweb management tool using your NDSU username and password, then click My Sites. Your Unix ID will be listed after the "Username" heading. 

Supported Clients 

Pubweb accepts secure connections only. You can use any client that supports SSH, SCP or SFTP protocols. This means FTP will not work--it is not secure. 

The following list is not an exhaustive list of compatible clients. 
  • PuTTY is an implementation of SSH and Telnet for Windows and Unix platforms, along with an xterm terminal emulator, released under the MIT license 
  • WinSCP is a free client for Windows that uses the SFTP protocol -- make sure to choose SFTP or SCP protocol and not FTP when you try to connect 
  • Dreamweaver can be configured to use SFTP -- when configuring a new site, set the Connect using field to SFTP 

Where to Put Files 

Basic site: Put files in your "public_html" directory. 

Enhanced site: Put files in the enhanced site directory -- you will recognize this folder by its name, which matches the organization name (as requested). 

File Permissions 

As you create files on Pubweb, you must pay attention to the permissions used on those files. If you are not comfortable changing file permissions or do not understand Unix file permissions, Pubweb is not an appropriate place for you to host web content. Instead you should use our supported web authoring platform (NDSU CMS). 

In the event you encounter a "403 forbidden" error, it is likely because the file is not readable by the web server. It may also be because it is contained in a directory that is not readable/executable, making the file unreachable. You can resolve by verifying all of the following: 
  1. The file must be owned by the appropriate group. For enhanced sites the group will match your enhanced site group name; for basic sites the group will be 'faculty.' If the correct group is not set, you must update to the correct group using 'chgrp' in a shell or your graphical SSH/SFTP client's permission management menus 
  2. The web server user must have read access to the file. A common permission bit values for files--including documents, images, and scripts--is 644 (-rw-r--r--) so that the web user (a member of your enhanced site group). If the correct permissions are not set, you must update the permissions using 'chmod' in a shell or your graphical SSH/SFTP client's permission management menus 
  3. The web server must have execute access to all directories in the path of the file. For example, if the file path is templates/images/file.jpg , then the templates and images directories must also have at least execute permission for the web server user. Common permission bit values for directories are 755 or 711 (-rwxr-xr-x or -rwx--x--x, respectively) so that the web server user can execute and possibly also read from the directory, depending on your preference. If the correct permissions are not set, you must update the permissions using 'chmod' in a shell or your graphical SSH/SFTP client's permission management menus 
Learn more about Unix file permissions:




Keywords:pub, host, publish, publishing, connecting, file, transfer, files   Doc ID:102081
Owner:Michael R.Group:Information Technology Division
Created:2020-05-14 13:07 CDTUpdated:2020-06-30 08:16 CDT
Sites:Information Technology Division
Feedback:  0   0