Forum Activity for @brian

brian
@brian
07/22/19 05:37:56PM
10,165 posts

403 Forbidden error after server migration


Installation and Configuration

Glad to see you back - it's been a few years :)

To view/change ownership you will probably have to use the file manager in your control panel - to be honest I am not sure how to do that, but hopefully that points you in the right direction.

Let me know if that helps.
brian
@brian
07/22/19 03:15:20PM
10,165 posts

SOAPI and Jamroom


Jamroom Developers

It's hard to say how much work this might involve. What is the name of the other system? It depends on what level of integration you are looking for. If this other system is containing the media, are you looking to just "import" it in to Jamroom and then run on Jamroom only, or are you looking to somehow "link" the 2? That would likely be a much larger amount of work, and likely not as performant.

Is there a feature in the other software that you are looking to use that makes you want to continue using it rather than just importing and moving to Jamroom?

Thanks!
brian
@brian
07/22/19 03:12:22PM
10,165 posts

403 Forbidden error after server migration


Installation and Configuration

Check the following:

1) You copied the .htaccess file in to the directory (most likely this is the issue)
2) Make sure the "jamroomdirectoryhere" is owned by the WEB USER and not your FTP account

Let me know if that helps.
brian
@brian
07/19/19 08:07:18AM
10,165 posts

Button to change account values


Using Jamroom

Something custom would have to be built - there's no mechanism to update a datastore key/value by pushing a button - sorry!
brian
@brian
07/19/19 08:06:43AM
10,165 posts

SOAPI and Jamroom


Jamroom Developers

Hi Matthias - unfortunately Jamroom has no support for SOAP API's, so something custom would have to be built specifically for this. I used to work with a SOAP API about 20 years ago - this isn't a protocol that is use much anymore. Is there an upgrade available for your other system that might allow it to use straight XML or JSON?

Thanks!
brian
@brian
06/21/19 10:29:40AM
10,165 posts

Cancel JamRoom Subscription


Using Jamroom

You have no server so you can't be charged, and we don't keep credit card numbers either, so you're all set.
brian
@brian
06/20/19 07:22:58PM
10,165 posts

Cancel JamRoom Subscription


Using Jamroom

Sorry to see you go.. here's a guide on deleting your Jamroom server:

https://www.jamroom.net/the-jamroom-network/documentation/jamroom-hosting/2933/deleting-a-jamroom-server

and please let us know the URL to your new site - we'd love to check it out :)

Let me know if that helps.

Thanks!
brian
@brian
05/28/19 08:47:22AM
10,165 posts

Gedcom import


Genosis

frdonly:And now I'm getting this:

"The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." instead of the site. Any idea what could have triggered this?

You want to contact your hosting provider - your server is underpowered for what you want to do. This is not a Jamroom error but an error from your server telling you it was unable to process your request "due to maintenance downtime or capacity problems".
brian
@brian
05/27/19 10:12:15AM
10,165 posts

Gedcom import


Genosis

frdonly:"Query Error: Lost connection to MySQL server during query:"

This is the root cause here - your MySQL server is crashing. It's probably running out of memory or connections, and is crashing. It shouldn't crash, but I suspect the MySQL server is misconfigured. You'll want to contact your hosting provider and have them check out the MySQL error log - it will have more info in it that can hopefully help them resolve the issue.

Let me know if that helps.
brian
@brian
05/27/19 07:58:54AM
10,165 posts

Gedcom import


Genosis

It doesn't sound like a memory issue to me - if it was, I don't think you'd even get past the parsing part and you would never see it creating the profiles. Since it stops at random places as well, and not at the same place every time, that tells me the GEDCOM file is correct and it's not hitting something it can't parse.

One thing to do is look in your jamroom's data/logs directory for an error_log - if you see that the last entries in that file can give us an idea of what might be going on.

Let me know if that helps.
updated by @brian: 05/27/19 07:59:12AM
  34