Data import from remote server fails with java.io.IOException: Method failedIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Data imported from a remote server fails and generates the following exceptions. This may occur for a scheduled import or when selecting Load All Records on the Data Source record. com.glide.db.impex.datasource.DataSourceException: com.glide.db.impex.datasource.DataSourceException: java.io.IOException: Method failed:(https://remoteserver/filename) null with code: 0 at com.glide.processors.ImportProcessorWorker.loadDataSource(ImportProcessorWorker.java:181) at com.glide.processors.ImportProcessorWorker.startWork(ImportProcessorWorker.java:104) at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:86) at com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:37) at com.glide.worker.ProgressWorkerThread.run(ProgressWorkerThread.java:53) Caused by: com.glide.db.impex.datasource.DataSourceException: java.io.IOException: Method failed: (https://remoteserver/filename) null with code: 0 at com.glide.db.impex.datasource.DataSource.getFile(DataSource.java:312) at com.glide.db.impex.datasource.DataSource.getFile(DataSource.java:252) at com.glide.db.impex.CSVLoader.setDataSource(CSVLoader.java:127) at com.glide.db.impex.JDBCLoader.setImportDataSource(JDBCLoader.java:551) at com.glide.db.impex.datasource.CSVDataSource.getLoader(CSVDataSource.java:21) at com.glide.processors.ImportProcessorWorker.loadDataSource(ImportProcessorWorker.java:139) ... 4 more Caused by: java.io.IOException: Method failed: (https://remoteserver/filename) null with code: 0 at com.glide.protocol.http.HTTPURLConnection.connect(HTTPURLConnection.java:38) at com.glide.protocol.http.HTTPURLConnection.getInputStream(HTTPURLConnection.java:46) at com.glide.db.impex.datasource.DataSource.writeFile(DataSource.java:336) at com.glide.db.impex.datasource.DataSource.getFile(DataSource.java:305) Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This issue occurs after applying ServiceNow Instance Hardening KB0550654 and setting the com.glide.communications.trustmanager_trust_all system property to false as a part of 9.1 Certificate Trust. By default, ServiceNow trusts a certificate's CA, which helps verify ServiceNow accepts self-issued certificates. When this property is set to false and the remote server is secured with a self-signed CA rather than a trusted CA, the import fails because the platform does not permit this connection. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } We recommend replacing the self-signed certificate on the remote server with a certificate issued by a trusted Certificate Authority (CA). This approach preserves the security controls introduced through Instance Hardening and is the recommended long-term solution. Please note that the procurement, creation, renewal, or installation of certificates falls outside the scope of ServiceNow support. As a platform provider, ServiceNow enables secure integration with customer-managed certificates but does not manage the certificate lifecycle on behalf of customers. For assistance with obtaining, renewing, or replacing a certificate, we recommend engaging your organization's Network, Infrastructure, or Security team. They will be best positioned to advise on your internal certificate requirements, approved Certificate Authorities, and the process for deploying the certificate within your environment. Once the trusted certificate has been installed on the remote server, we will be happy to assist with any ServiceNow-side validation or integration testing as needed.