I am using the community version of jasperserver 8.0.0, I have to clarify that I have not made any changes or alterations in jasperserver other than working with localhost, now my next step is for other people to connect to the server, the problem is that the information on the internet about this is scarce, my question is what are the steps to achieve this and something like http://172.20.1.70:8080/...
Related
I know this question has been asked before, but none of those solutions seem to have worked for me so far.
We've migrated our database over to and IBM cloud hosted mongoDB. I've got the connection working successfully for our .NET applications that use the Mongo.Driver library, but i can't get it work for our meteor app... Here's the connection string I have currently:
mongodb://admin:[PASSWORD]#url1.databases.appdomain.cloud:31928,url2.databases.appdomain.cloud:31928,url3.databases.appdomain.cloud:31928/dyo?authSource=admin;tls=true;tlsInsecure=true;connect=replicaSet;replicaSet=replset
I then run the connection string in this command:
SET MONGO_URL=[connection string shown above] && meteor --settings settings.json
And then we just get the error you see in the title over and over again. This happens on our galaxy server and locally. I feel like i should get this working locally first before deploying to our Galaxy server. Does anyone have any tips as to what could be happening here? I'm new to working with mongodb's and am at a loss
More info:
MongoDB version: 4.4
Meteor version: 1.4.4.1
I ended up fixing our connection issue by including ssl=true in the connection URL and removing all the parameters relating to TLS. I believe this has to do with our older version of meteor we are running, since ssl=true is actually deprecated later on...
Here's a github issue i also created if anyone has the same issue and needs more guidance in the future:
https://github.com/meteor/meteor/issues/12224
I apologize for the amateur nature of my question, but I am all rather new to this. So I have created a project within the cloud9 IDE, which is a website that connects to a mySQL database located on the same server. However, I wish to showcase the code that I have used to create the site. I have done a little research into doing this and so far I have found that GitHub Pages can allow you to host webcontent. Thus in theory I can just copy across the files from cloud9 to a GitHub repository. However, my site relies on being able to connect to and query a mySQL database. My question is, can and how would I connect my GitHub repo to such a database?
Any help/advice would be greatly appreciated! In addition, please let me know if I am barking up the wrong tree with this...
GitHub Pages are only for static HTML websites. It does not run any server side technology.
You must find web hosting based on the technology you used to create the website.
If you've been working on a server-side technology, then you could be running on localhost.
If thats the case, try tunnelling your localhost, which allows you to share your localhost with others on other networks.
localtunnel, ngrok and forward provide such technologies.
I have bought a VDS (Virtual Dedicated Server) that Windows Server 2008 is installed on it. I needed to use server because I have developed a C# console application that can read data by TCP socket and write them in the MySQL database.
Now I need to start a website on this server. I think WAMP server is so easy for me.
Maybe in future a lot of people visit my website.
Is it a good idea to use WAMP server as a web server?
In principal there is nothing wrong with using WAMPServer as a LIVE webserver.
However, not the out of the box version.
Out of the box WAMPServer and XAMPP for that matter expect to be used as a single seat developer tool and while that is great for a click and go solution to get a developer up and running on Apache/MySQL and PHP in a few minutes it is not secure enough to be considered as a LIVE web facing webserver.
Now if you have the knowledge and experience to create an user account on Windows Server that has access to only what Apache needs to do its work, and can get Apache to run in that account instead of its default account (which has way to many privilages for a live server) and are prepared to explore all the Apache security features/modules that would be required for a web facing server then it is possible. However this is not a trivial task, and any mistakes or ommissions will leave your server open to the simplest of hacks.
In short, unless you really know what you are doing with Windows Server and Apache, you would be far better to pay for a professionally configured and managed web server environment.
I know this question has been asked several times but I have a slight variance on it that I have been trying to resolve.
I have crystal reports running on an old web system written in classic asp. All the reports have been running without problems for several years, however recently security was improved so that the system is now accessed over HTTPS. Since this change the reports have all started asking for the database credentials. If SSL is disabled so that it returns to regular HTTP then they start working again.
The system was created by another developer who has since moved on so I am not very familiar with it, but as far as I am aware the reports are all set to use a System DSN set up in the control panel of the server that IIS is running on. The database is located on a separate server.
Does anybody have a suggestion as to why the reports would start asking for database credentials after changing to HTTPS and how to resolve it? I will not be able to make any code changes to the application as the source code is not available but I can modify the reports and play with connection settings etc.
I have figured out the problem. The site was running HTTPS but the button for the report was in a form which submitted to HTTP and then was redirected back to HTTPS. This was causing a loss of the session information or something like that. Fortunately the forms action url was stored in the database so it was a simple matter to resolve.
I have a DNN site (5.06) that I developed on a standalone machine running IIS7. When I copied the site to the production machine running IIS6 and enter the URL, such as www.site.com, I get a generic DNN error page with no additional information. However, if I add the default page, www.site.com/Default.aspx everything works fine.
The Friendly URL settings were never changed and I've verified Default.aspx is entered on the Documents tab in IIS6. The portal event viewer has no entry for the error page I get.
I'm nearly certain it has to do with migrating from IIS7 to II6; clearly I'm missing something here. Any ideas?
DNN has confirmed this is an error in 5.06, and will be addressed in a future update. That doesn't help me today, but I was able to work around the problem by adding the following to the Friendly URLs list:
Look for: .*/
Send To: ~/Default.aspx
I can't find the forum thread I was reading yesterday, but did find this one which also goes into detail on the issue: Error upgrading from 5.5.1 to 5.6.0
Pretty odd...
Double check PortalAlias table in your SQL server. Confirm www.site.com is in there.
Double check host headers in IIS6 has www.site.com
Make sure Default.aspx is in the documents area of IIS6 and set as the top default to run
Recycle your app pool
cross your fingers
Only thing I ever run into from IIS6 and IIS7 is in the app pool running in Integrated mode or classic... but that is usually as issue going from IIS6 to 7, not vice versa.
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have the correct machine key and connection strings. This is my last resort when DotNetNuke is being strange. I am running 10+ DNN sites at version 5.6.0 and I only encountered this issue once.