Magento Integration
Sync inventory, pull sales information, sync products to and from Magento. Magento can also be used just to process payments without managing inventory.
Note: Cin7 Core supports Magento 2. See Magento 2.0 Integration for more information.
Note: If using translation or localisation apps in Magento, ensure that base attribute values (colour, etc.) are in English. Base attribute values not in English can cause problems when listing products.
NOTE: When a refund is processed for an unfulfilled sale, this will cause an error with restocking the unfulfilled items. These will appear on the Log as Pending fulfillment. If you are experiencing this error, you will need to enable the Ignore restock for non-fulfilled sales setting. This setting is not enabled automatically in order to preserve system logic continuity for users.
Prerequisites
Admin access to Magento (necessary)
Familiarity with sales (necessary)
Familiarity with Products and Product Management (necessary)
Users will need to Integration: eCommerce - Magento permission in order to use this feature.
Users will need to add an External integration licence to their subscription if they do not have one available.
Magento Integration Setup
First, you must connect Cin7 Core to your Magento store. You will need admin access to Magento to set up the integration. Users will need to add an External integration licence to their subscription if they do not have one available. Additional external integrations must be purchased from the My Subscription page.
Setup in Magento
To prepare for the integration in Magento:
Log in to the admin panel of your Magento store.
Create a new Role in your Magento store. Go to System → Web Services → SOAP/XML-RPC – Roles.
You will see the list of roles in your Magento shop. For a new installation, this list will be empty.
Click Add New Role.
In the Role Info tab, name the role and enter the admin password.
In the Role Resources tab, set Resource Access to All. Click Save Role.
Create a new User and assign it to this Role. Go to System → Web Services → SOAP/XML-RPC – Users.
Click Add New User.
In the User Info tab, fill in the mandatory fields. User Name and API Key will be required to integrate with Cin7 Core. All the other fields are just general information required for Magento user registration.
Click on User Role on the left and select the newly created role for this user. Click on Save User to save changes.
Update permissions for the new role (here, named Guest). Go to System → Web Services → REST – Roles.
Click the newly created Guest Role from the list to open permissions.
Set Resource Access is set to All. Click Save Role to save your changes.
Connecting Magento to Cin7 Core
It is possible to link several Magento stores to a single Cin7 Core account. Each linked store has an independent catalog, logs and settings. Cin7 Core provides two free external integrations with the standard subscription plan, however, additional external integrations must be purchased from the My Subscription page.
To connect Magento to Cin7 Core:
Navigate to Integration → Magento.
Click + to connect a new store.
Enter your Magento shop details and click Connect to Magento.
You will be redirected back to Cin7 Core. Repeat these steps to connect as many Magento accounts as you require.
Integration settings
In the Setup tab, several integration settings can be customised.
Order Capture
This option specifies when a Magento Order will be captured: when it is created, when it is fulfilled or when it is paid in Magento. This setting is also taken into account when downloads of historical orders from Magento are triggered.
Consolidate Orders
Cin7 Core - Magento Integration allows two options for order consolidation:
No Consolidation
Daily Consolidation.
No Consolidation indicates that sales will be captured from Magento as they occur. Daily Consolidation will consolidate all orders from that day into a single order. When Daily Consolidation is chosen, an additional setting becomes available: Consolidation Time. This is your local time when all pending orders aggregated during the day will be processed.
See Pending Order Processing section for more details below.
Customer
For the pending order processing to be successful, an existing customer must be selected.
When the Consolidation Type is Daily Consolidation, this customer is used to create a new sale task which will combine all daily sales. A customer can be created in Cin7 Core just for this purpose.
Use Company as a Customer
This parameter only has an effect when the No Consolidation option is selected.
In Magento, each sale order has an optional Company field which can be filled in by a customer. If you would like Cin7 Core to create a customer using the company name (as opposed to the Customer name attached to the sale order in Magento), this option should be selected.
Price Tier
Choose which Price Tier to use as the default price when Cin7 Core syncs products with Magento. See Pricing and Price Tiers for more information.
Pick, Pack and Ship Processing Mode
When pending orders are processed by Cin7 Core, new sale tasks are created. This setting tells Cin7 Core if it should try to Auto Pick, Auto Pack and Auto Ship these tasks. If there is not enough stock on hand to pick the full quantity of products in an order, then Pick will remain in Draft state and Pack and Ship won’t be completed.
Cin7 Core does not pick up shipment information from Magento if auto-ship is selected and will not create fulfilment in Magento in this scenario (if Auto Ship is enabled).
Process Auto-Assembly as
This dropdown field has two options:
For ordered quantity: Does not check stock quantity. An assembly order is created for the quantity specified in the sale order, regardless of stock availability.
-
For minimum quantity required for picking:Assemble stock required to meet the quantity of specific sale order.
If stock availability is negative, auto-assembly will produce a finished goods quantity which is more than the quantity ordered through sale order.
If there is already stock available in inventory but not enough to fulfill the sale order quantity, auto-assembly will assemble the difference in quantity needed to meet the sale order requirement.
If stock availability exceeds sale order quantity, auto-assembly is not triggered.
Stock availability is validated against the sale order location and does not take On Order quantity into account
Ignore Restock for non-fulfilled sales
When a refund is processed for an unfulfilled sale, this will cause an error with restocking the unfulfilled items. These will appear on the Log as Pending fulfillment. If you are experiencing this error, you will need to enable this setting. Restock/stock allocation quantities will be edited to match the fulfilled items of the sale. This setting is only applicable when Pick, pack, and ship mode for processing online sales is set to Auto Pick + Pack + Ship.
Link Magento sales to Cin7 Core Location
Magento does not allow the use of multiple warehouses. Each Magento store can have a dedicated Location within Cin7 Core which can be selected from the drop-down menu. Selecting a particular warehouse will limit the availability of stock in Magento to that location. The default option, All Locations, will display consolidated stock quantities across all of your locations.
Invoice Status
You can control Invoice Status for Sale tasks created as a result of pending order processing. By default, an invoice will not be authorized and will be in Draft state, adjustable and waiting for authorization. However, if this setting is changed to AUTHORISED, the invoice will be automatically authorized and pending sync will be created for it to sync with an accounting application of your choice.
Gift Card Liability Account
Cin7 Core will use this Liability account instead of a Revenue account for Gift Card sales. This account should have the ability to accept payments. If a sale is made which contains a gift card, this sale will remain in the Pending Orders area until Gift Card Liability Account is specified.
Optional revenue account
This is the revenue account to be used for all sales downloaded from Magento. This will override settings at the Product/Customer level and any other Account mapping.
Sales Representative Name
This option allows the shop name to be used as a Sales Representative.
Update Stock Levels in Magento
You may choose to disable automatic stock level update in Magento performed by Cin7 Core at the time available product quantity changes in Cin7 Core. This may be useful if you are managing stock level in Magento manually and do not want Cin7 Core to change it. Please ensure you have the correct stock quantities entered in Cin7 Core before you turn on this option as these values will override the stock quantities in Magento. Enabling Update Stock Levels in Magento will display the Use Buffer Inventory setting.
Use Buffer Inventory
Displayed when Update Stock Levels in Magento is enabled. Allows for an inventory buffer on stock quantities pushed to Magento. Sync quantity passed to Magento when updating stock levels will be equal to Actual Stock - Buffer Inventory. Enabling this setting will enable the Buffer Inventory field.
Buffer Inventory
Displayed when Use Buffer Inventory is enabled. Enter an integer number of stock to act as a buffer. Sync quantity passed to Magento when updating stock levels will be equal to Actual Stock - Buffer Inventory. When this setting is enabled, Sync Quantity and Buffer Inventory quantity will be added as fields to the Catalog and Bulk Listing tables alongside stock availability.
Note: Once buffer inventory is enabled and specified, it will be applied across all products listed on the Catalog and Bulk Listing tabs. However, sync quantities will only be updated in the channel if the user updates or lists a product.
Send email from Magento
When enabled, this sends an email to the customer from Magento when shipping has been authorized.
Tax Rule Mapping
When a pending order is processed by Cin7 Core, a sale task is created. Each order and invoice line is assigned a tax rule. The tax rules specified in these settings will be used to create these lines.
Cin7 Core does not apply the tax rule to recalculate tax and is simply using the actual tax amount from the Magento order. This means that if certain products are not Taxable or with varying tax in Magento, all data and totals in Cin7 Core will look identical to Magento, but with Cin7 Core tax rule name selected in this setting.
The Tax Free tax rule mapping specified in this setting is used to create these lines for non-taxable products. This tax mapping could be useful for accounting.
In the case of tax recalculation, the Tax amount will be overwritten with the value calculated by the Cin7 Core Taxation rule.
IMPORTANT: Orders will be skipped on download if Taxation mapping is not finished!
Note: For US Magento stores, the provided Sales Tax is used instead of Tax Rule mapping.
Payment Account Mapping
Cin7 Core can capture payments made against orders in Magento and is able to automatically add payments to a created sale invoice. To do this, Payment Account Mapping must be completed on this integration settings screen. You must choose an account which is able to receive payments from the chart of accounts.
This setting is not mandatory – if payment mapping is not completed, orders are still captured and downloaded from Magento, but payments must be manually added to invoices in Cin7 Core. Some customers prefer to keep invoices open and then reconcile them with payouts from Magento.
Disconnect from Magento store
When you disconnect from the Magento store, Cin7 Core removes all associations between Cin7 Core objects and Magento, including Log and Product Catalog.
Catalog
The Cin7 Core Magento Catalog page allows the user to Download products from Magento, list Cin7 Core products on Magento, break the link between a Cin7 Core product and its Magento listing and update quantities in Magento according to Cin7 Core available stock.
Downloading Products
Products can be loaded from Magento to Cin7 Core in the Catalog tab by clicking Download → Products. This operation may take some time.
Each product variation in Magento must have a unique SKU. Configurable products require individual simple products for each variation. These simple products will have individual SKUs in Cin7 Core.
When a product is created/updated in Cin7 Core during the download process, a link is established between item unique Magento ID and Cin7 Core unique product ID. This link is used when products are matched against sale order lines in Magento and when subsequent product download occurs to update the same products.
Magento supports Product Families but all Product Family variants are downloaded as simple products. This is due to performance issues of Magento SOAP API during loading.
Magento Product Types are mapped to Cin7 Core categories.
When downloading products, Cin7 Core tries to match existing products first to avoid creating duplicates. Matching is performed by item or variant SKU.
Data mapping for products between Cin7 Core and Magento is as follows:
Cin7 Core |
MAGENTO |
SKU |
Listing SKU if defined, otherwise first 50 characters from combination of (Product title + Option 1 Value + Option 2 Value + Option 3 Value) |
Name |
Product title + Option 1 Value + Option 2 Value + Option 3 Value |
Category |
Product Type |
Description |
HTML Product Description |
Weight |
Weight (Converted to KG) |
Barcode |
Barcode |
Price Tier. Default is Price Tier 1 |
Price |
Images |
Small product image |
Product Tags |
First 256 characters of Product Tags |
Option 1 Value |
Option 1 Value |
Option 2 Value |
Option 2 Value |
Option 3 Value |
Option 3 Value |
Manage the Catalog
There are two possible statuses for products in the Catalog: Not Listed and Listed. To be listed, every item needs to have a description, item image and default location specified.
Note: Cin7 Core does not update category or images for an existing product in Magento, category and images are pushed only upon product creation.
Note: Cin7 Core products can only be synced as a simple product (not a bundle) in Magento even if it was configured with a bill of material in Cin7 Core. Cin7 Core product families are synced as configurable products in Magento. This is due to a limitation of the integration.
Note: Updating products from the catalog will update the stock level in Magento regardless of the Update Stock Levels in Magento setting status.
To list or update a product on Magento:
Click on the product in the Catalog tab.
In the pop-up window, specify the Attribute Set (this is required). It is required to specify the Magento Attribute Set in order to create a product in Magento. Cin7 Core products must have an Attribute Set specified to be listed.
You can enable or disable stock level syncing at the individual product level.
Click List on Magento for a product which has not yet been listed or Update on Magento for a product which has already been listed.
Save your changes.
To unlist a product on Magento:
Click on the product in the Catalog tab.
Click Unlink.
Save your changes.
To remove a product from Magento:
Click on the product in the Catalog tab.
Click Remove from Magento.
Save your changes.
Bulk Listing
Products from your Cin7 Core inventory can also be listed in bulk. If products are already listed, this action will update them.
When Use Buffer Inventory setting is enabled from the Setup tab, Sync Quantity and Buffer Inventory quantity will be added as fields to the Bulk Listing tables alongside stock availability. See Buffer Inventory for more information.
To list products on Magento in bulk:
Go to the Bulk Listing tab.
Select products to upload in bulk. You can select by Category, Brand, Family, Product Tag, Attribute Set, Listing Status, Currency, and Products Listed in (another channel), and through manual search.
Note: If you have multiple stores in another sales channel, e.g. two different Shopify stores, these will be displayed separately in the list of sales channels from which products can be selected for upload.
Specify an Attribute Set for the product. It is required to specify the Magento Attribute Set in order to create a product in Magento. Cin7 Core products must have an Attribute Set specified to be listed.
Select Currency. If you are using markup pricing, a currency conversion will be performed between the Cin7 Core base currency and the selected currency. If you are using static pricing, the price tier value will be passed to Magento unchanged.
Click List to upload all selected products to Magento. You can also Unlist and Unlink products in bulk in the same way.
Buffer Inventory
Instead of showing actual inventory values in e-Commerce storefronts, many retailers prefer to display an estimated display quantity where there is a safe buffer stock on their backend to avoid overselling products. Cin7 Core allows for an inventory buffer on stock quantities pushed to Magento, both for the whole channel and at the product level.
Buffer inventory levels for the whole channel are controlled from the Setup tab. Update Stock Levels in Magento setting must be enabled.
Use Buffer Inventory: Displayed when Update Stock Levels in Magento is enabled. Allows for an inventory buffer on stock quantities pushed to Magento. Enabling this setting will enable the Buffer Inventory field.
Buffer Inventory: Displayed when Use Buffer Inventory is enabled. Enter an integer number of stock to act as a buffer. Sync Quantity passed to Magento when updating stock levels will be equal to Actual Stock - Buffer Inventory.
When this setting is enabled, Sync Quantity and Buffer Inventory quantity will be added as fields to the Catalog and Bulk Listing tables alongside stock availability. However, sync quantities will only be updated in the channel if the user updates or lists a product.
Buffer Inventory for the whole channel can be overwritten by a product level buffer from either the Catalog or Bulk Listing page (Use buffer inventory must be enabled from the channel Setup tab). The product level buffer value will ALWAYS override the value set on the Setup tab. If the Setup tab buffer inventory value is changed, this will not affect products with product level buffers.
Note: Product level inventory buffer is disabled by default. In the case of wanting to turn off inventory buffer for certain products only, the user will need to enable buffer inventory and enter a value to apply it to the whole catalog, THEN set product level buffer to 0 for those products, then update or list the item to apply changes.
If the user wishes to apply inventory buffer ONLY to one or more specific products, inventory buffer should be enabled on the Setup tab and set to 0. Then, product level buffer inventory can be enabled and configured for products from either the catalog or bulk listing page. You will need to list or update the item to apply changes.
On the Catalog page:
Click on a listed or unlisted item to open a pop-up window and slide Use Product Level Buffer Inventory to enable. You can then enter an integer value for Product level buffer which will overwrite the channel buffer value. You will then need to Update or List the product for the new stock level quantity to be displayed in the channel. Save and Close to continue.
On the Bulk Listing page:
Use this to update product level buffer for multiple items at once. Use the search box and filter options to filter items to list/update in bulk.
The Use Buffer Inventory menu allows you to Turn on product level setting, Remove product level setting, or Don't update existing setting.
Turning on product level setting allows you to then enter an integer value for Product level buffer. Click List to overwrite the channel buffer value for the filtered products with the product level buffer.
Selecting Remove product level setting, then List, will remove the product level setting from the filtered products and return them to the channel buffer inventory value.
Selecting Don't update existing setting will leave all buffer values, including product-level buffer values, unchanged when updating listings or making a new listing.
Orders and Sales
Processing Pending Orders
When a Magento store is connected to Cin7 Core, automatic notifications are triggered when orders are created, when their status is changed, and when they are cancelled or deleted.
Depending on the Order Capture setting selected, Cin7 Core will capture a Magento Order and save it as pending order when the Order is created, fulfilled or paid. Sometimes it takes up to 10 minutes for the order to be picked up by Cin7 Core because Magento may send notifications with some delay.
Whenever a sale is captured from Magento it is first placed into Pending Orders, and stock is allocated immediately. Cin7 Core imports new orders immediately as individual sale orders (if No Consolidation is selected in the Integration Settings) or once a day as a consolidated sale order (if Daily Consolidation is selected).
If No Consolidation is selected, each Magento sale is converted into an identical sale in Cin7 Core, keeping the same customer and shipping information. If Daily Consolidation is selected, the single daily sale task will use the customer selected in the integration settings, and customer, billing and shipping information imported from Magento will be ignored.
When a Magento order is cancelled or deleted, Cin7 Core automatically finds and voids the corresponding sale task, if created, or removes an associated pending order if the order has not yet been processed.
When processing orders, the logic is identical to that of the Cin7 Core UI. DropShipping, Kitting and other important scenarios are implemented in the same way as through the Cin7 Core UI.
Pending Orders can be processed manually by clicking Process. They can then be viewed in the Log tab.
Downloading Customers
Customers can be loaded from Magento to Cin7 Core in the Catalog tab by clicking Download → Customers.
This function downloads all customers from Magento to Cin7 Core. If the customer already exists in Cin7 Core, this function updates any details that have been changed in Magento. As Cin7 Core automatically creates customers when processing sale orders (if the No Consolidation option is selected), this function is generally only used for testing purposes.
This function creates a customer in Cin7 Core with Contact, Billing and Business addresses captured from Magento. Customers cannot be uploaded from Cin7 Core to Magento.
Downloading Orders and Payments
Orders are automatically downloaded if their status in Magento is changed (for example, a customer pays for an order).
Note: Generally, you do not need to trigger manual order download, however, if an order was not captured by Cin7 Core or to load historical sales, you can use the manual Load Order option.
Any imported order is saved to the Pending Orders section. It is a temporary storage of all sales and payments in Cin7 Core. If an order already has an entry in the Log (i.e. was imported previously) it will be skipped. This guarantees that no duplicate sales will be created by Cin7 Core.
Pending Orders can be processed manually by clicking Process, which writes the orders into Cin7 Core as sales tasks. They can then be viewed under the Log tab.
While saving orders, Cin7 Core captures customer information, billing and shipping addresses. All line items are captured together with quantities, prices and totals. Total order discounts are applied as are additional charges to the whole order, without distribution by lines to reduce the chance of discrepancy.
Shipping and handling are also saved as additional charges in the Sale invoice under Shipping.
If a Payment Account has been specified in the Integration Settings, Cin7 Core will always assign associated payments to the captured Magento orders.
When a Magento order is cancelled, Cin7 Core automatically finds and voids the corresponding sale task if already created as a Sale Order or just removes the associated pending order if not yet processed.
The final step in the order download is to trigger the update of stock levels in other Magento stores and other connected eCommerce channels. This is performed by clicking Update Quantities in Magento from the Catalog tab.
Updating Fulfilment in Magento
When Shipment is authorized in Cin7 Core and the carrier specified, Cin7 Core will try to create order shipment information in Magento. This will only work in the No Consolidation processing mode.
Logs
Each captured Magento order once saved to Pending Orders creates a Log entry to track the link between the Sale in Cin7 Core and in Magento. This eliminates the possibility of creating duplicated orders when capturing the same order several times during manual order load.
Each Log entry has a link to the sale task in Cin7 Core. Depending on the settings selected by the user in the Setup tab, this sales task could be draft or authorized, one or more of the Pick, Pack and Ship tabs could be authorized, and payment could have been applied to the invoice.
Log entries allow you to see which Sale task reflects a particular Magento sale. You also have the option to delete a Log entry manually. This will allow reprocessing an order if required. Deleting a log entry will not void or delete its associated sale task.
To delete a specific log record, click the Delete icon. This allows the sale task to be reprocessed, if required.
Reloading Orders from Magento
If for any reason you need to reload an order from Magento, this can be managed from Cin7 Core. Cin7 Core allows loading historical sales data a maximum of one year old.
To reload an order from Magento:
Void the sale task. A record of this will be kept in Cin7 Core for reconciliation purposes but the transactional data will be deleted.
Return to the Magento integration Log tab and delete the Log entry. This will allow the order to be recaptured from Magento.
Navigate to the Pending Orders tab and click Load Orders, making sure the date is set to before the order to reload was made. Cin7 Core allows loading historical sales data a maximum of one year old.
Refunds
Cin7 Core captures refunds from Magento. Cin7 Core will then capture the refund and return/restock and apply them to the associated sale task.
Please note that if the sale is unfulfilled, this will cause an error with restocking the unfulfilled items. These will appear on the Log as Pending fulfilment. If you are experiencing this error, you will need to enable the Ignore restock for non-fulfilled sales setting.
Submit returns request via RMA portal
Customers can submit returns requests via Cin7 Core RMA Portal if your organization subscription has this feature, allowing customers to initiate the Cin7 Core RMA workflow, and view the status of their returns. This includes sales processed through connected eCommerce channels.
Any Cin7 Core customer can submit a returns requests via the returns portal with an order number or invoice number and email address simply by accessing the relevant URL. We recommend adding the URL to the return portal to your default sale email template sent to customers. c
Please note that refunds/restocked processed in this way will not be automatically exported to the eCommerce channel, and will have to be added manually updated within the channel. You may prefer to use the returns workflow offered by Magento if you do not need the additional RMA workflow features in Core.
Refunds for sales predating integration with Cin7 Core
Merchants with eCommerce channels occasionally have to process returns or refunds for a sale that predates integration of the eCommerce channel with Cin7 Core.
Sales and refund information is imported automatically from the eCommerce channel to Cin7 Core, but can also be manually imported via the Cin7 Core web portal. Historical refunds and returns are handled differently for each case.
Automatic import: Cin7 Core checks the sale order date against the date of integration with the eCommerce channel. If the sale order date predates the date of integration, credit note and refund are imported without the corresponding historical sale task.
A sale is created without order lines or invoice lines.
Credit note tab shows refunded items and if a refund was processed in the eCommerce channel it will be captured on this tab.
Restock tab is left empty and no stock adjustments are made.
Manual import: Manually loading orders from Magento functions in the same way whether the sale took place before or after integration with Cin7 Core.
From the Pending Orders tab, click Load orders and select a date to load sales, including historical sales as Pending Orders. Process the sale associated with the refund.
The sale order with have order, invoice, pick, pack, and ship lines. It will also have credit note and restock lines.
User will have to perform a manual stock adjustment to correct any discrepancies from the refund.
Logs
Each captured Magento order once saved to Pending Orders creates a Log entry to track the link between the Sale in Cin7 Core and in Magento. This eliminates the possibility of creating duplicate order records when capturing the same order several times during manual order load.
Each Log entry has a link to the sale task in Cin7 Core. Depending on the settings selected by the user in the Setup tab, this sales task could be draft or authorized, one or more of the Pick, Pack and Ship tabs could be authorized, and payment could have been applied to the invoice.
Log entries allow you to see which Sale task reflects a particular Magento sale. You also have the option to delete a Log entry manually. This will allow reprocessing an order if required. Deleting a log entry will not void or delete its associated sale task.
Note: During sale events, there can be a large spike of transactions created within a very short time period. This requires a large number of queries to sync all of the orders to Cin7 Core. Magento limitations on large numbers of queries can lead to delays in data loading and updates to related operations such as stock level updates, shipment updates, etc.
To handle these cases, an automatic backend configuration which checks for sales spikes and temporarily disables sale capturing and stock level updates to Cin7 Core when Magento API capacity is close to being exceeded. The pending sales will be logged and then uploaded with a single API call at 5 minute intervals. Sales created during the disabled period will be uploaded to the “Logs” table with the newly implemented status, “To be loaded” to process them later. Manual loading of sales is not affected and the setting will automatically be returned to normal when the sales spike is over.
Troubleshooting
Still no answer to your question? Please do not hesitate to get in touch with Cin7 Core support.
Pending orders not loading
A common Magento error is when orders are placed via the Magento website but do not come through to Cin7 Core. When trying to load orders, this error message appears:
This error is caused b incorrect Magento server configuration, it can't call itself by the external domain name. Magento API calls itself while executing API calls.
While the WSDL URL (http://remote_host/index.php/api/index/index/wsdl/1/) can be loaded from your computer, your remote server can't contact itself via its REMOTE_HOST.
PHP's SoapServer object (used by Magento's implementation) needs to contact the WSDL to know which methods are exposed.
For reasons unknown, it's a common network configuration for a server to not have access to its own DNS entries. Connect to your server via SSH and try running the following:
curl http://remote_host/index.php/api/index/index/wsdl/1/
It is most likely you'll get a network timeout or a REMOTE_HOST unknown error. Fix your configuration so your server can access itself, and everything should start working.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB