Jump to content

YongSan

Community Leader
  • Content count

    587
  • Joined

  • Last visited

  • Days Won

    3

YongSan last won the day on May 25 2017

YongSan had the most liked content!

Community Reputation

2 Neutral

About YongSan

  • Rank
    Cloud Master
  1. Technically it is possible to restore emails back to the server using a method. But we do not recommend you to try this as it is having some drawbacks. However, if you still want to restore the emails back to the server, please follow the steps provided below, Create a second email account in your profile using the IMAP account type. You'll now have two accounts in your profile for the same email account, with the IMAP account adding a second *.pst to the profile. Make sure you set the POP3 account to leave mail on the server in the account's More Settings. Advanced dialog. Drag the messages from the POP3 Inbox to the IMAP folder's Inbox. Tip: You may want to start with about 100 messages at a time and wait a minute or so for the messages to sync up. If it works well, select a larger block of messages to move in the second batch. The messages will be synced with the mailbox on the server. When finished, remove the IMAP account from the profile. (unless you want to use it instead of POP3.) Note: This, however, has one drawback, it will remove the original timestamp and will show you the time stamp of the day when the outlook was sync with the mail server. Also, there is a possibility of missing emails on the mail server due to syncing issues.View the full article
  2. ReadySpace Customer portal are different depending on which branch you purchased the services. (Refer to Customer Portal) 1. Login to your Customer Portal 2 Select appropriate subscription from drop down menu (located at top right of the interface) 3. Click on "Email" tab on the top. 4. Click on the Email address 5. Click on Spam protection Tab 6. If you find a button "Disable" then you have already enabled the spam protection, if not please click on the button "Enable" to enable Spam filtering.7. Click on Edit to manually setup Spam action and Spam threshold value to 3.5. 7. Set the Spam Action as Delete NOTE: Spam Action Delete: If "Delete" option is selected, then any Email's that are detected as spam will be automatically deleted. Mark as spam: If "Mark as spam" is selected, Email's that are detected as Spam will be only quoted as Spam and is kept in the Inbox itself. Mark as spam and modify subject: If "Mark as spam and modify subject" is selected, then the Email's that are detected as Spam will be quoted as you want it to be viewed. NOTE: If you set the Spam Action as Delete, there are chances of missing genuine emails due to which false identification of the genuine emails as spam. In this case, we request you to raise the Spam threshold value to a bit higher and monitor the mailbox to see which value suites best for you. View the full article
  3. ReadySpace Customer portal are different depending on which branch you purchased the services. (Refer to Customer Portal) 1. Login to your Customer Portal 2 Select appropriate subscription from drop down menu (located at top right of the interface) 3. Click on "Email" tab on the top. 4. Click on the Email address 5. Click on Spam protection Tab 6. If you find a button "Disable" then you have already enabled the spam protection, if not please click on the button "Enable" to enable Spam filtering.7. Click on Edit to manually setup Spam action and Spam threshold value to 3.5. 7. Set the Spam Action as Delete NOTE: Spam Action Delete: If "Delete" option is selected, then any Email's that are detected as spam will be automatically deleted. Mark as spam: If "Mark as spam" is selected, Email's that are detected as Spam will be only quoted as Spam and is kept in the Inbox itself. Mark as spam and modify subject: If "Mark as spam and modify subject" is selected, then the Email's that are detected as Spam will be quoted as you want it to be viewed. NOTE: If you set the Spam Action as Delete, there are chances of missing genuine emails due to which false identification of the genuine emails as spam. In this case, we request you to raise the Spam threshold value to a bit higher and monitor the mailbox to see which value suites best for you. View the full article
  4. 1. install ntpdeamon (if not installed already) # yum install ntp 2. Simply open /etc/ntp.conf file, enter: # vi /etc/ntp.conf 3. Replace the lines which starts with "server" with the below ones (Eg:- server ntp.server.com) server 0.sg.pool.ntp.org server 1.sg.pool.ntp.org server 2.sg.pool.ntp.org server 3.sg.pool.ntp.org 4. Add cron job to sync the time automatically. # echo '30 * * * * root /usr/sbin/ntpd -q -u ntp:ntp' > /etc/cron.d/ntpd View the full article
  5. The sudo command provides a mechanism for granting administrator privileges, ordinarily only available to the root user, to normal users. This guide will show you the easiest way to create a new user with sudo access on CentOS, without having to modify your server's sudoers file. If you want to configure sudo for an existing user, simply skip to step 3. Steps to Create a New Sudo User Log in to your server as the root user. ssh root@server_ip_address Use the adduser command to add a new user to your system. Be sure to replace username with the user that you want to create. adduserusername Use the passwd command to update the new user's password. passwdusername Set and confirm the new user's password at the prompt. A strong password is highly recommended! Set password prompts: Changing password for user username. New password: Retype new password: passwd: all authentication tokens updated successfully. Use the usermod command to add the user to the wheel group. usermod -aG wheel username By default, on CentOS, members of the wheel group have sudo privileges. Test sudo access on new user account Use the su command to switch to the new user account. su - username As the new user, verify that you can use sudoby prepending "sudo" to the command that you want to run with superuser privileges. sudocommand_to_run For example, you can list the contents of the /root directory, which is normally only accessible to the root user. sudo ls -la /root The first time you use sudo in a session, you will be prompted for the password of the user account. Enter the password to proceed. Output: [sudo] password for username: If your user is in the proper group and you entered the password correctly, the command that you issued with sudo should run with root privileges. View the full article
  6. First, log in to the Plesk panel of the server. Then, to see the list of services, go to Tools & Settings > Server Management > Services Management. The icon next to the name of a service indicates that it is currently running. The icon indicates that the service is currently stopped. To start, stop and restart a service To start a service: Click the icon corresponding to the service you wish to start. To stop a service: Click the icon corresponding to the service you wish to stop. To restart a service: Click the icon corresponding to the service you wish to restart. View the full article
  7. First, log in to the Plesk panel of the server. Then, to see the list of services, go to Tools & Settings > Server Management > Services Management. The icon next to the name of a service indicates that it is currently running. The icon indicates that the service is currently stopped. To start, stop and restart a service To start a service: Click the icon corresponding to the service you wish to start. To stop a service: Click the icon corresponding to the service you wish to stop. To restart a service: Click the icon corresponding to the service you wish to restart. View the full article
  8. Note : Please allow access to the following domains to your firewall as these are the mirrors used to download the script packages. api.softaculous.com (IP : 192.198.80.3) s1.softaculous.com (IP : 158.69.6.246) s2.softaculous.com (IP : 192.200.108.99) s3.softaculous.com (IP : 178.32.158.97) s4.softaculous.com (IP : 138.201.24.83) s7.softaculous.com (IP : 167.114.200.240) Installing Softaculous Using GUI NOTE: This method can be used for Plesk 12.0+. Login to your Plesk Control panel with user which has root previliges Go to Server Management >> Extensions page and click on the Extensions Catalog tab Search for Softaculous and click on the Install button This is depicted in the image below: The installation process starts once you click on 'install'. You will be notified once the installation is completed successfully. Installing Softaculous Using CLI NOTE: This method is for older versions of Plesk. Note: Before starting the installation make sure ionCube Loaders are enabled. Otherwise you will not be able to Install Softaculous. The ionCube Loaders can be downloaded from here. You can also check if ionCube is enabled with the following shell command : root> php -m | grep -i ioncube Note: Also make sure POSIX is enabled. Otherwise you will not be able to Install Softaculous. You can check if POSIX is enabled with the following shell command : root> php -m | grep -i posix Now SSH to your server and enter following commands: wget -N http://files.softaculous.com/install.sh chmod 755 install.sh ./install.sh The Installer will start showing the Installation Processes and when done will indicate the same. NOTE: Scripts will be downloaded during this process. The Download Activity will also be shown on the screen. Thats it the installation of Softaculous is completed! You will see the following screen. Quick Installation If you wish to finish the installation quickly and then download the script packages in background use this method. Note: Before starting the installation make sure ionCube Loaders are enabled. Softaculous Installer requires Ioncube. Now SSH to your server and enter following commands: wget -N http://files.softaculous.com/install.sh chmod 755 install.sh ./install.sh --quick View the full article
  9. The below guide shows: Where to log in to your SpamExperts control panel How to create an outgoing mail user. What data to use for setting up your SPF For more detailed information, we always recommend consulting the SpamExperts' knowledge base, which should have the most detailed and up-to-date information, at kb.spamexperts.com. 1) Login to your customer portal at Customer Portal. 2) Navigate to your SpamExperts or Office mail subscription (whichever applicable) 3) Click the "SpamExperts" Tab and protect the domain if it was not protected yet. Then click the "Login" button next to the domain name. 4) In the SpamExperts control panel, navigate to Outgoing > Manage users 5) from the manage users page, you can create a new user using any of three forms of authentication, via IP address or IP range, via user, or via domain. If you don't know which you need, we recommend consulting the SpamExperts knowledge base article getting started with outbound. To configure your sender policy framework (SPF), please use the below provided SPF record. SPF record "v=spf1 a:spf.cleverspeed.com -all" 6) Then you need to set up your server mail transfer agent (MTA) to work with SpamExperts, In order to achieve this, please refer to the following SpamExperts knowledge base article MTA configuration. View the full article
  10. The below guide shows: Where to log in to your SpamExperts control panel How to create an outgoing mail user. What data to use for setting up your SPF For more detailed information, we always recommend consulting the SpamExperts' knowledge base, which should have the most detailed and up-to-date information, at kb.spamexperts.com. 1) Login to your customer portal at Customer Portal. 2) Navigate to your SpamExperts or Office mail subscription (whichever applicable) 3) Click the "SpamExperts" Tab and protect the domain if it was not protected yet. Then click the "Login" button next to the domain name. 4) In the SpamExperts control panel, navigate to Outgoing > Manage users 5) from the manage users page, you can create a new user using any of three forms of authentication, via IP address or IP range, via user, or via domain. If you don't know which you need, we recommend consulting the SpamExperts knowledge base article getting started with outbound. To configure your sender policy framework (SPF), please use the below provided SPF record. SPF record "v=spf1 a:spf.cleverspeed.com -all" 6) Then you need to set up your server mail transfer agent (MTA) to work with SpamExperts, In order to achieve this, please refer to the following SpamExperts knowledge base article MTA configuration. View the full article
  11. These instructions assume you've already exported your Outlook email, contacts, and calendar from another instance of Outlook, and now you want to import them to Outlook 2013, Outlook 2016, or your Office 365 mailbox. At the top of your Outlook 2016 or 2013 ribbon, choose File. If your ribbon doesn't have a File option in the top left corner, you aren't using an Outlook app installed on your computer. See What version of Outlook do I have? to find your version of Outlook and to get to right import steps. Choose Open & Export > Import/Export. This starts the wizard. Choose Import from another program or file, and then click Next. Choose Outlook Data File (.pst) and click Next. Browse to the .pst file you want to import. Under Options, choose how you want to deal with emails and contacts, then choose Next. If a password was assigned to the Outlook Data File (.pst), enter the password, and then click OK. If you're importing the contents of your .pst file into your Office 365 mailbox, choose that mailbox here. If you're NOT importing into your Office 365 mailbox, choose Import items into the current folder. This imports the data into the folder currently selected. Choose Finish. Outlook starts importing the contents of your .pst file immediately. It's finished when the progress box goes away. If you're importing your .pst file to your Office 365 mailbox, you may see a message that it's trying to connect with Office 365. This happens when the Internet connection is interrupted, even for a moment. Once your Internet connection is re-established, Outlook will continue importing the .pst file. TIP: If you want to retrieve only a few emails or contacts from an Outlook Data File (.pst), you can open the Outlook Data File, and then, in the navigation pane, drag and drop the emails and contacts from .pst file to your existing Outlook folders. View the full article
  12. 1. Using the CDP Server web interface you can browse the files and folders on your Agent's hard disk and select the files and folders to include in the backup. 2. You can optionally add complex rules to exclude files by a pattern. For example, *.log or *.mp3. 3. Your selected folders and exclude rules are communicated to the CDP Agent at the beginning of every backup operation. 4. CDP Agent (Windows and Linux) takes a point-in-time block level snapshot of the backup target. 5. The CDP Agent mounts the virtual snapshot device. For example, X: drive (Windows) or /mnt/snapshot (Linux). Note These mounted devices are invisible to users and do not conflict with other mount points or drives. 6. According to the selected files/folders and exclude rules the Agent proceeds to delete all excluded files and folders from the writable snapshot using simple userspace delete methods. Note This deleting is only done in your point-in-time snapshot and does not affect your real disk volume and data. View the full article
  13. OACI REST API Basics

    OACI REST API Basics The OACI RESTful API provides programmatic access to REST resources. Using the API you can obtain information about the resources and perform actions on them. For example, you can obtain a list of the existing servers, start or stop a server, modify server configuration, create a new or delete an existing server, and perform many other management tasks. This chapter provides an overview of the API and describes the basics of using it in your programs. Accessing a Resource A OACI resource is accessed by sending an HTTPS request to a OACI server. When the server receives a request, it processes it accordingly (performs actions or retrieves data) and sends back a response that can contain the data that you requested, an operation status code, or an error message. All OACI resources are accessed at the following base URL (referred to as baseURL in the API reference topics of this guide): https://{ip_address | hostname}:port/paci/version where: ip_address | hostname is the OACI server IP address or hostname. port is the port number on which the server is listening for REST requests paci must be typed exactly as shown version is the API version number Note: Ask your service provider for the values listed above (except the "paci" string) and then use them when composing the base URL in your code. Base URL example The following base URL sample contains the OACI server hostname ("paci-web"), port number (4465), the "paci" string, and the version number (v1.0). https://paci-web:4465/paci/v1.0 Resource path and parameters When accessing a particular resource, you append the following values to the base URL: The path that identifies the resource Optional resource-specific parameters (where available) Each resource is identified by a path within the base URL. An individual resource may have subresources within its own path, each of which is also identified by a path. For example, the following sample URL references the ve resource, which is "server" in general: https://paci-web:4465/paci/v1.0/ve The following sample URL references a specific server identified by its name, which in this instance is my-server-01: https://paci-web:4465/paci/v1.0/ve/my-server-01 Resource-specific parameters Some requests allow to specify additional (usually optional) parameters. For example, when obtaining the list of the operating system templates, you may add a filter to retrieve the templates for a particular operating system (e.g. a particular Linux distribution). Additional parameters are included in the URL after the question mark (?). HTTP Request Headers When sending an HTTPS request, the request headers must contain authentication and content type information as described below. Authentication OACI REST API uses the basic authentication scheme as defined by RFC 1945 (Hypertext Transfer Protocol – HTTP/1.0). An HTTP request header must contain credentials in the form of user name and password separated by a colon and encoded using the Base64 encoding scheme. The following is an example of an authorization header: Authorization: Basic dG9ib3RyYXM6cTE= Please note that the password to be used in OACI REST API calls must be obtain from the Operations Automation customer's control panel as follows: In the customer's control panel, open the Cloud Infrastructure tab. Switch to the API Access tab and click the Generate API Access Key button. Your key appears in a message box. Use this key as the password in your API calls. Service providers can obtain the REST API access key using the provider's control panel. Please see the provider's guide for additional information. Content Type Input data is included in the OACI REST API request in the form of an XML document. Therefore, Content-type should be specified as "application/xml": Content-type: application/xml Callbacks OACI REST API provides a callback functionality that allows you to receive responses from OACI server asynchronously. To use a callback, the request header must include the "x-callback-url:" string followed by the URL at which your HTTP server listens for callbacks from OACI server. For example: x-callback-url: http://192.168.3.77:8081/bd6fsdb4-24sd-4a64-8fd1-403d1b11tf0a HTTP Methods REST requests are sent to the OACI server as HTTP POST, GET, PUT, and DELETE messages. In many cases different methods can be used on the same resource to achieve different goals. For example, you can obtain the information about a server using the GET method, modify its configuration using the PUT method, and delete it using the DELETEmethod. The resource (identified by a path) will be the same in all three instances, but each request parameters and input/output data will be different. In this guide, each API reference topic describes a particular operation and provides information about the HTTP method that must be used. Data Input and Output When sending or receiving data, it is included in a request or received from the OACI server as an XML document. Each request that sends or receives data has a corresponding XML specification that defines the XML document structure. When composing a request, the specification must be followed precisely. The validation of the request is performed on the server side against the XML specification. If a mandatory parameter is missing or an invalid parameter is passed, you will receive an HTTP error. An XML specification for each request and response is described in individual request topics of this guide. The sample XML document below contains a server information. A document like this is received when a server information is requested or is included in the request when a new server is created (or an existing server is modified). <?xml version="1.0" encoding="UTF-8"?> <ve> <name>my-server-01</name> <description>Test server</description> <cpu number="2" power="1600"/> <ram size="512"/> <disk local="true" size="1"/> <platform> <template-info name="ubuntu-9.10-x86_64"/> </platform> <backup-schedule name="daily"/> </ve> In general, the same XML specification is used in the API for input and output when dealing with the same resource type. Certain parameters, however, cannot be used in the input version and therefore must be omitted. The reference topics in this guide describe the input and output XML specifications separately. Error Handling If there's an error executing a OACI REST API request, an HTTP page containing the error information is returned to the caller. The page contains an HTTP code and the description of the error. HTTP error 406 usually means that there was an error in the request or the operation cannot be completed for other reasons. In this case, the error page will also contain a OACI REST API error code and a text describing the error. The following is an example of such code and description: P80100: Template [centos-6-x86_64] is already registered at the node ... The code in the example above (P80100) can be interpreted as follows: The first letter can be either P (permanent error) or T (transient error). The first digit after the letter means one of the following: 1 — internal error 2 — resource is in use 3 — resource is not available 4 — unsupported operation 5 — invalid modification 6 — the operation cannot be performed at this time 7 — the request is missing required information 8 — invalid data was passed in the request 9 — invalid operation The rest of the number is formed by multiplying the first digit by 10000 and adding an actual error code to it. In the example above, the actual error code is 100, therefore: 8 * 10000 + 100 = 80100. HTTP errors other than 406 could mean other, usually general, errors and will contain a proper description of the problem. Format and Conventions The baseURL convention The string "baseURL" is used in the API reference topics as a shorthand for the base URL at which the OACI resources can be accessed. When composing an HTTP request, the "baseURL" string must be substituted with the base URL specific to your OACI environment. API reference topics Each API reference topic in this guide provides information on how to compose an HTTP request that will perform a particular operation on a particular resource. Each entry contains the following information: An HTTP method (POST, GET, PUT, DELETE) used to access the resource. Depending on the type of the operation, different methods may be used to access the same resource. Each operation type has its own topic in this documentation. A full path to the resource in the form baseURL/resource_path. A description of the resource and the operation. A list of additional parameters that can be used with the request (where applicable). An XML specification of the input and/or output XML documents (included only with the requests that send and/or receive data). Use these specifications to compose an XML input and parse the XML output. Samples of HTTP request, HTTP response, and input/output XML documents. To compose an HTTP request that will perform a particular task on a particular resource, find the corresponding reference topic (each topic name contains the short task description) and follow the provided instructions. API reference format Each topic describing an HTTP request has the following sections: Description Explains the purpose of the request. Syntax Specifies which HTTP method is used with the request (GET, POST, PUT, DELETE) and the resource URL. Request Parameters Describes the XML specification used to specify the request parameters. Response For requests that don't output data, describes the HTTP message returned. For requests that return data, describes the XML Schema of the output XML document. Example Provides samples of HTTP request, HTTP response, and XML input/output. Testing code samples and creating your own programs You can test the samples provided in this guide using a REST client for a Web browser. For example, you can use a simple but effective RESTClient extension for Firefox or any other available REST plug-in and a browser of your choice. To write your own programs using the API, you will need a development tool that will allow you to make Web requests from the command line or from a program (e.g a program written in C or Python). One of the commonly used tools is cURL. With cURL you can use the API in a script or a C program. View the full article
  14. Steps 1. Login into the web interface of the cloud drive at https://drive.readyspace.com 2. Navigate to the patch from which the files were deleted. 3. Check the "deleted files" from the top menu. 4. Recently Deleted files and folders will be shown on the list marked with a little trashcan on the file icon. 5. By clicking/ or right-clicking the file, a menu/or pop-up will be shown and you can see history and you can undelete the file. Please refer to the screenshot attached for reference. Screenshot View the full article
  15. Steps 1. Login into the web interface of the cloud drive at https://drive.readyspace.com 2. Navigate to the patch from which the files were deleted. 3. Check the "deleted files" from the top menu. 4. Recently Deleted files and folders will be shown on the list marked with a little trashcan on the file icon. 5. By clicking/ or right-clicking the file, a menu/or pop-up will be shown and you can see history and you can undelete the file. Please refer to the screenshot attached for reference. Screenshot View the full article
×